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

690 scenarios

Continue learning →

Module · Perceivable

1.3.2 — Meaningful Sequence

The reading order in the code must match the order that makes sense visually.

A 0 / 20 Open lesson

Empty Elements Making Screen Readers Announce ‘Blank’ Repeatedly

1.3.2 A

Empty elements or stray whitespace in the code are announced as 'blank' — often several times in a row — adding meaningless stops between real content for screen reader users.

Visible Page Text Completely Skipped by the Screen Reader

1.3.2 A

Visible text content is skipped entirely by the screen reader (missing from the accessibility tree) — sighted users see information that assistive technology users never encounter at all.

Several Distinct Controls Merged Into One Announced Item

1.3.2 A

Several distinct controls are merged into one announced item — size options or share buttons read as a single blob, so screen reader users cannot reach or operate them individually.

Module · Perceivable

Checkpoint gate

Checkpoint 16: Scenarios 151–160

Practice scenarios 151–160 before continuing

Take checkpoint

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.