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 · Understandable

3.1.1 — Language of Page

The page's language must be declared in code (lang attribute) and be correct.

A 0 / 8 Open lesson

Page Published With No Language Declared in the Code

3.1.1 A

No numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).

HTML Element Missing Its Language Attribute Entirely

3.1.1 A

<html> lacking lang entirely.

Page’s Declared Language Not Matching Its Actual Content

3.1.1 A

Wrong lang (template shipped lang="en" on a Hindi/Arabic/French site) — screen readers use wrong speech synthesizer.

Language Attribute Set to an Invalid or Malformed Value

3.1.1 A

Invalid values: lang="english", lang="EN-UK", region codes malformed beyond recognition.

Language Switcher That Doesn’t Update the Page’s Lang Attribute

3.1.1 A

single-page app localization switching UI language without updating document.documentElement.lang.

Language Attribute Set on the Body Instead of the HTML Root

3.1.1 A

lang on <body> instead of <html> in contexts where assistive technology reads the root.

Multilingual Site Serving Every Locale With the Same Lang Value

3.1.1 A

Multi-lingual sites serving all locales from one template with hard-coded original language.

PDF Document Published With No Language Metadata Set

3.1.1 A

PDFs without the /Lang document entry.

Module · Understandable

Checkpoint gate

Checkpoint 53: Scenarios 521–530

Practice scenarios 521–530 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.