WCAG 2.2 Guidelines

Practical, developer-ready guidance for WCAG 2.2—what’s new, what to build, and how to test.

What’s new in WCAG 2.2

WCAG 2.2 adds 9 new Success Criteria and removes 4.1.1 Parsing. Conformance to 2.2 implies 2.1/2.0 (backwards-compatible). [1]

  • 2.4.11 Focus Not Obscured (Minimum) – AA
    Focused elements must be at least partially visible (avoid sticky UI hiding focus). [2]
  • 2.4.12 Focus Not Obscured (Enhanced) – AAA
    Focused element fully visible. [3]
  • 2.4.13 Focus Appearance – AAA
    Clear, sufficiently contrasting focus indicator. [4]
  • 2.5.7 Dragging Movements – AA
    Provide a single-pointer alternative to drag (e.g., buttons to move/resize). [5]
  • 2.5.8 Target Size (Minimum) – AA
    Targets are at least 24×24 CSS px or have sufficient spacing. [6]
  • 3.2.6 Consistent Help – A
    Keep help mechanisms in a consistent location across pages. [7]
  • 3.3.7 Redundant Entry – A
    Don’t make users re-enter info in multi-step flows; prefill or offer “use previous”. [8]
  • 3.3.8 Accessible Authentication (Minimum) – AA
    Avoid cognitive tests; allow password managers, copy/paste, passkeys, etc. [9]
  • 3.3.9 Accessible Authentication (Enhanced) – AAA
    Same intent, stricter coverage. [10]

AA checklist (build & test)

Cover these high-impact AA areas, including the new 2.2 items.

Focus & Keyboard

  • Every control reachable with Tab / Shift+Tab; no traps.
  • Visible :focus-visible outline with good contrast. (2.4.11/2.4.13) [11]
  • Focused item not hidden by sticky headers/footers. (2.4.11) [12]

Pointer & Target size

  • Alternative to drag for all functionality. (2.5.7) [13]
  • Targets ≥ 24×24 CSS px or sufficient spacing. (2.5.8) [14]

Forms & Auth

  • Explicit labels; helpful errors; programmatic state.
  • Don’t ask for info twice in one process. (3.3.7) [15]
  • Allow paste / managers / passkeys; avoid cognitive tests. (3.3.8) [16]

Help & Process

  • Place help links or contact in a consistent spot across pages. (3.2.6) [17]
  • Full pages and complete processes meet the target level (not just single screens). [18]

Conformance (how WCAG is “met”)

  • Levels: A, AA, AAA. Policy targets are typically AA. [19]
  • Full pages & complete processes: every step must meet the level. [20]
  • Accessibility-supported tech and no content that violates the success criteria. [21]
  • Backwards-compatible: 2.2 adds to 2.1/2.0; 4.1.1 removed. [22]

Testing workflow (practical)

  1. Automated rules (GetWCAG) for quick catches.
  2. Keyboard sweep: confirm focus visibility and not obscured. (2.4.11) [23]
  3. Pointer checks: verify 24×24 or spacing; no required dragging. (2.5.7/2.5.8) [24]
  4. Auth: allow paste & managers; offer passkeys / email link. (3.3.8) [25]
  5. Multi-step flows: retain data; consistent help location. (3.3.7 / 3.2.6) [26]

“No automated issues” ≠ conformance. Manual review is required.

FAQ

If I meet 2.2 AA, do I meet 2.1 AA?

Yes—WCAG 2.2 is additive to 2.1/2.0 (except 4.1.1 removed). [27]

Is AAA required?

Usually no. Treat AAA (e.g., 2.4.12, 2.4.13, 3.3.9) as stretch goals unless policy mandates them. [28]

Official references
  1. What’s new in WCAG 2.2 (W3C)
  2. Understanding 2.4.11
  3. Understanding 2.4.12
  4. Understanding 2.4.13
  5. Understanding 2.5.7
  6. Understanding 2.5.8
  7. Understanding 3.2.6
  8. Understanding 3.3.7
  9. Understanding 3.3.8
  10. Understanding 3.3.9
  11. Focus appearance guidance
  12. Focus not obscured guidance
  13. Dragging movements
  14. Target size minimum
  15. Redundant entry
  16. Accessible authentication (min)
  17. Consistent help
  18. Conformance basics
  19. WCAG overview
  20. Full pages & processes
  21. Accessibility-supported
  22. New in 2.2 / 4.1.1 note
  23. Keyboard sweep ref
  24. Pointer & target size
  25. Auth checks
  26. Process consistency
  27. 2.2 implies 2.1/2.0
  28. AAA context
WCAG 2.2 Guidelines (AA Focus) — Practical Guide