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.1.1 — Non-text Content

Every meaningful image, icon, chart, or other non-text object needs a text alternative that serves the same purpose, while purely decorative images must be hidden from assistive technology.

A 0 / 34 Open lesson

Lazy-Loaded Image Whose Alt Text Never Finishes Loading

1.1.1 A

Placeholder/lazy-load images whose final alt never populates (JS injects alt late or never).

Mood-Only Hero Image Given an Overly Detailed Alt Description

1.1.1 A

Stock "hero" images that convey mood only but are exposed with verbose, distracting alts (should be decorative).

Decorative Bullet Symbols Read Aloud by Screen Readers

1.1.1 A

Decorative Unicode glyphs used as visual bullets or dividers (■ ▶ ✦) announced literally by screen readers ("black square") with no aria-hidden (code hiding content from screen readers) handling.

Alt Text So Long It Buries the Image’s Real Purpose

1.1.1 A

Alt text is excessively verbose — a full scene description of every visual detail — burying the image's actual purpose — screen reader users sit through paragraphs where a short, purposeful description was needed.

Module · Perceivable

Checkpoint gate

Checkpoint 4: Scenarios 31–40

Practice scenarios 31–40 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.