WCAG 2.2 Accessibility Scenario Learning Hub

A guided course for learning accessibility through realistic, industry-grounded product scenarios. Each scenario carries a unique real-world example, plain-language explanation, and a direct reference to the official WCAG 2.2 Understanding document.

Progress 0 / 690

219 scenarios

Continue learning →

Module · Operable

2.4.6 — Headings and Labels

Headings and labels must describe their content/purpose.

AA 0 / 9 Open lesson

Form Label Like ‘Field 1’ That Doesn’t Describe Its Purpose

2.4.6 AA

Labels that don't describe the field's purpose: "Field 1", bare "*", "Enter value".

Same Label Used for Two Different Fields on One Form

2.4.6 AA

Ambiguous duplicate labels ("Name" for both product and user in one form).

Clever Marketing Heading That Hides What a Section Actually Does

2.4.6 AA

Marketing-clever but opaque headings on task UIs ("Let's go!" as sole label of a critical section).

Button Labeled ‘OK’ on a Destructive, Irreversible Action

2.4.6 AA

Button labels not describing action ("OK" for destructive delete confirmation).

Two Date Fields Both Labeled ‘Date’ With No From/To Distinction

2.4.6 AA

Date range fields both labeled "Date" with no from/to distinction.

Heading That Actually Describes the Section Before It

2.4.6 AA

Headings describing the previous section due to placement errors.

Module · Operable

2.4.7 — Focus Visible

Keyboard focus must always be visible.

AA 0 / 11 Open lesson

Element Losing Keyboard Focus the Instant It’s Reached

2.4.7 AA F55

As soon as an element receives keyboard focus, a script throws focus away (blur) — keyboard users can never actually reach or use it.

Focus Outline Removed by CSS With No Replacement

2.4.7 AA F78

CSS removes or hides the focus outline (outline:none / border removal) with no replacement — keyboard users can't see where they are on the page.

Global CSS Reset Removing Every Focus Outline Site-Wide

2.4.7 AA

Global CSS reset *:focus{outline:0} with no:focus-visible (keyboard-focus styling) replacement.

Focus Indicator Styled for Some Components but Not Others

2.4.7 AA

Custom indicator present only for some components (links styled, buttons not).

Glossary

Accessible name: The short name assistive technology uses for a control — often from a label, aria-label, or associated text.
Alt text (text alternative): The written description of an image that screen readers read aloud instead of the image.
ARIA: A set of HTML attributes that explain roles, names, and states to assistive technologies when native HTML is not enough.
Assistive technology (AT): Tools people with disabilities use to operate software: screen readers, magnifiers, voice control, switch devices.
Contrast ratio: A measured difference between text (or a graphic) and what sits behind it; higher ratios are easier to see.
Focus / keyboard focus: The single element currently 'selected' by the keyboard — where Enter/Space/typing will act. Moved with Tab.
Focus indicator: The visible highlight that shows which element currently has keyboard focus.
Focus order / tab order: The sequence elements are reached when pressing Tab repeatedly.
Keyboard trap: A situation where keyboard focus moves into a component and cannot move out using standard keys.
Landmark: A page region such as banner, navigation, main, or contentinfo that screen-reader users can jump between.
Live region / status role: Markup (for example aria-live or role="status") that tells screen readers to announce updates without moving focus.
Programmatically determinable: Available in code so software — not only human eyes — can read the information reliably.
Reading order: The order assistive technology reads content, which follows the DOM sequence rather than pure visual placement.
Screen reader: Software such as NVDA, JAWS, VoiceOver, or TalkBack that speaks or brailles interface content and controls.
Semantic markup: Using HTML elements that match meaning (headings, lists, tables, buttons) instead of generic styled containers alone.
Viewport: The visible browser area. Reflow testing often uses about 320 CSS pixels of width.