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.1 — Info and Relationships

Structure you can SEE (headings, lists, tables, labels, groups, required marks) must also exist in the code so screen readers perceive the same structure.

A 0 / 49 Open lesson

Out-of-Stock Status Shown Only Visually, Never Announced

1.3.1 A

Availability states shown only visually — an option greyed out or struck through as 'out of stock', or stock info like '4 left' — are never announced, so screen reader users pick unavailable options or miss urgency.

Tooltip Help Text Never Linked to Its Trigger Control

1.3.1 A

Tooltip or help text tied to a control (an info icon's explanation) is visible on screen but never announced — it isn't programmatically linked to the control, so screen reader users focus the control and get none of the guidance sighted users see.

Same Page Content Accidentally Announced More Than Once

1.3.1 A

The same content is announced twice — duplicated accessible nodes, or a landmark (a coded page region) re-announced with all its links on every encounter — creating noise and making users doubt where they are.

Module · Perceivable

Checkpoint gate

Checkpoint 14: Scenarios 131–140

Practice scenarios 131–140 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.