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.3 — Focus Order

Keyboard focus must move through the page in an order that makes sense.

A 0 / 21 Open lesson

Disabled Controls Still Included in the Keyboard Tab Order

2.4.3 A

Disabled controls included in the tab order, adding dead stops.

Decorative Element Wrongly Given a Keyboard Tab Stop

2.4.3 A

Non-interactive text or decorative graphics given tabindex (keyboard-focus setting), inserting meaningless focus stops.

Focus Resetting to the Top After Loading More Content

2.4.3 A

After activating a load-more/expander control, focus resets to the top of the page instead of continuing at the injected content.

Failed Form Submission Sending Focus to the Wrong Field

2.4.3 A

After a failed form submission, focus jumps to the wrong place — the last error instead of the first, or somewhere unrelated, so keyboard users fix errors out of order or hunt for them.

Activating a Control That Throws Keyboard Focus Elsewhere

2.4.3 A

Activating a control (a filter checkbox, a Next button) throws keyboard focus somewhere else instead of keeping it on the control — the user loses their place after every action.

Escape Key Closing the Wrong Layer in a Nested Dialog

2.4.3 A

Pressing Esc inside a nested layer (a dropdown or combobox open inside a modal) closes the entire modal instead of just the innermost layer — the user is dumped out mid-task and loses their work in the dialog.

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.