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.1 — Bypass Blocks

There must be a way to skip repeated blocks (header/nav) — usually a 'Skip to main content' link.

A 0 / 9 Open lesson

Skip Link Placed After the Navigation It’s Meant to Skip

2.4.1 A

Skip link placed after the nav it's meant to skip.

Landmarks Used as a Bypass but Missing Key Content

2.4.1 A

Landmarks used as the mechanism but content sits outside main, or multiple identical unlabeled landmarks (coded page regions) defeat navigation.

Bypass Mechanism With No Heading to Land On

2.4.1 A

Headings used as the mechanism but the main content has no heading to jump to.

Skip Link That Jumps to the Wrong Part of the Page

2.4.1 A

Skip link points to wrong location (skips into mid-content or to footer).

Single-Page App That Loses Its Skip Link After Navigation

2.4.1 A

single-page app route changes rebuilding the page without any bypass because the "skip" only existed on first load.

Module · Operable

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.