WCAG 2.2 AA (Web Content Accessibility Guidelines)
WCAG 2.2 Level AA is the W3C international standard for web accessibility, current as of October 2023. WCAG 2.2 added 9 new success criteria to WCAG 2.1, covering focus appearance, dragging movements, target size, redundant entry, and accessible authentication. Level AA is the practical conformance target for most production sites and the 2026 practitioner standard.
Also called: WCAG 2.2 Level AA, WCAG 2.2 · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
WCAG (Web Content Accessibility Guidelines) is the international consensus standard for accessibility. Version 2.2 was published October 5, 2023, adding 9 new success criteria. Level AA is the most commonly targeted conformance level — A is too lenient for legal defensibility, AAA is too restrictive for many design contexts. WCAG 2.2 AA is the 2026 practitioner gold standard.
How it works.
WCAG 2.2 has 86 total success criteria organized into 4 principles (POUR: Perceivable, Operable, Understandable, Robust). Level A criteria (50) are minimum; Level AA (24 additional) is the recommended standard; Level AAA (12 additional) is the highest. Conformance requires meeting all criteria at the targeted level. WCAG 2.2 added 9 criteria to WCAG 2.1: focus appearance, dragging movements, target size (minimum), focus not obscured (minimum + enhanced), consistent help, redundant entry, accessible authentication (minimum + enhanced).
2026 reality check.
WCAG 2.2 has been the practitioner standard since late 2024. WCAG 3.0 (currently in W3C Working Draft) is years away from Recommendation status. The new 2.2 criteria (target size, redundant entry, accessible authentication) catch real-world failures that older WCAG versions missed — particularly around mobile UX and authentication flows. Federal procurement is gradually shifting from WCAG 2.0 AA references to WCAG 2.2 AA.
Data points
- WCAG 2.2 published October 5, 2023
- 86 total success criteria across 4 principles (POUR: Perceivable, Operable, Understandable, Robust)
- Level AA = 50 (Level A) + 24 (additional) = 74 criteria required
- Added 9 new criteria vs WCAG 2.1 (target size, redundant entry, accessible authentication, etc.)
- Maintained by W3C Web Accessibility Initiative (WAI)
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy targets WCAG 2.2 AA on every site we build. Our methodology: semantic HTML5 foundation (header, nav, main, article, section, aside, footer with proper heading hierarchy), ARIA only where native HTML cannot express the pattern, axe-core + Pa11y automated CI testing, manual NVDA + JAWS + VoiceOver screen reader validation, keyboard-only navigation testing, color-contrast verification at design-system level. WCAG 2.2 AA is documented via VPAT 2.5 INT for federal engagements.
How TDG approaches it
TDG's WCAG 2.2 AA stack: semantic HTML5 foundation, axe-core + Pa11y in CI, manual NVDA/JAWS/VoiceOver testing, keyboard-only navigation verification, color contrast validated at design-system level, target size enforced (24x24 min), focus appearance designed explicitly, consistent help patterns across sites, redundant entry minimized in forms.
Common mistakes.
- Targeting WCAG 2.0 AA when WCAG 2.2 AA is the 2026 practitioner standard
- Using accessibility overlays instead of building accessibility into the code
- Skipping manual screen reader testing (automated tests miss ~30-40% of real accessibility issues)
- Failing to meet target size criterion (interactive elements must be 24x24 CSS pixels minimum)
- Forgetting consistent help criterion (help links/buttons must appear in consistent locations across pages)
FAQ.
What's new in WCAG 2.2 vs 2.1?
9 new success criteria: focus appearance, dragging movements, target size (minimum), focus not obscured (minimum + enhanced), consistent help, redundant entry, accessible authentication (minimum + enhanced).
Why target AA instead of AAA?
AAA includes criteria that conflict with common design decisions (very high contrast ratios, sign language for video). AA is the practical conformance target. AAA is achievable in specific contexts but rarely site-wide.
Does WCAG 2.2 AA require accessibility overlays?
No — WCAG explicitly does not require any particular technology. Overlays do not produce true WCAG conformance. The standard is met by building accessibility into the code.
How is WCAG 2.2 different from Section 508?
WCAG is the international technical standard (W3C). Section 508 is U.S. federal law that adopts WCAG 2.0 AA by reference. WCAG 2.2 AA exceeds the Section 508 legal minimum.
When will WCAG 3.0 launch?
Currently W3C Working Draft. Years away from Recommendation status. WCAG 2.2 remains the production standard until 3.0 is finalized.
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term