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

121 scenarios

Continue learning →

Module · Understandable

3.2.1 — On Focus

Merely focusing (tabbing to) an element must not cause big changes — no popups, no navigation, no focus jumps.

A 0 / 9 Open lesson

Keyboard Focus Triggering an Unexpected Scroll Jump

3.2.1 A

Focus triggering scroll-jacking that relocates the user to a different section (context change).

Tabbing Into a Field That Opens a Chat Widget

3.2.1 A

Focus opening a chat widget that steals focus.

Autofocus Chain That Jumps Focus From One Field to Another

3.2.1 A

Autofocus chains: focusing field A programmatically jumping focus to field B.

Focus-Triggered Tooltip That Traps or Reroutes Keyboard Focus

3.2.1 A

Tooltip-on-focus that traps or reroutes focus rather than just showing content.

Radio Button That Selects Itself Just From Receiving Focus

3.2.1 A

A control is activated or selected merely by receiving keyboard focus — e.g., radio buttons that auto-select while the user tabs through them — changing values the user never chose.

Module · Understandable

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.