Guide · updated September 2026
WCAG 2.2, explained like a human
WCAG 2.2 (published October 2023) is the current version of the guidelines everyone measures you against. It keeps everything from 2.1 (one criterion retired: 4.1.1 Parsing) and adds nine criteria. Only a few change your daily work — here's the honest triage.
The new criteria that actually matter
- Focus not obscured (2.4.11, AA) — your sticky header or cookie banner must not hide the element a keyboard user has focused. The most common new failure we find.
- Redundant entry (3.3.7, A) — don't make people re-type information you already collected in the same flow. Checkout killers love this one.
- Accessible authentication (3.3.8, AA) — no memorizing or transcribing puzzles to log in; allow paste and password managers.
- Dragging movements (2.5.7, AA) — anything draggable needs a click alternative.
- Target size minimum (2.5.8, AA) — tap targets at least 24×24 CSS pixels, with spacing exceptions.
The rest — consistent help placement (3.2.6), focus appearance at AAA (2.4.13), and friends — matter, but the five above are where audits and lawsuits are already citing 2.2.
2.1 vs 2.2 — which should you target?
Regulators still write "2.1 AA" (the EAA's EN 301 549, most DOJ settlements). But 2.2 AA contains 2.1 AA, plaintiff experts have started citing 2.2 criteria, and building to 2.2 costs barely more. Target 2.2 AA; you're covered under every current regime.
Sources: W3C WCAG 2.2 Recommendation (Oct 2023); EN 301 549. Educational content, not legal advice.