WCAG 2.2 Recommendation
The latest evolution of WCAG, introducing 9 new success criteria focused on low vision, cognitive accessibility, and touch screen usability.
Technical Scope & Purpose
WCAG 2.2 builds upon WCAG 2.1 by addressing practical modern user needs. It also removed the obsolete Success Criterion 4.1.1 (Parsing), recognizing that modern browsers now handle HTML parsing errors consistently.
Core Requirements & Success Criteria
2.4.11 Focus Not Obscured (Minimum) (AA)
When an element receives keyboard focus, it must not be completely hidden by author-created content (such as sticky headers, cookies banners, or floating buttons).
2.4.12 Focus Not Obscured (Enhanced) (AAA)
When an element receives keyboard focus, no part of its focus indicator may be obscured.
2.4.13 Focus Appearance (AAA)
The focus indicator must have an area of at least 2px border or equivalent contrast ratio of 3:1 against surrounding colors.
2.5.7 Dragging Movements (AA)
Any function requiring a dragging movement (such as drag-and-drop kanban boards or sliders) must also offer a single pointer alternative (e.g., clickable up/down buttons).
2.5.8 Target Size (Minimum) (AA)
Interactive pointer targets must be at least 24 by 24 CSS pixels, or provide sufficient spacing to adjacent targets to prevent accidental clicks.
3.2.6 Consistent Help (A)
If a digital product provides help (contact form, chat widget, phone number, FAQ), the link or access point must appear in the same relative order across pages.
3.3.7 Redundant Entry (A)
Information previously entered by the user in a multi-step process must either be auto-populated or available for selection, reducing cognitive load.
3.3.8 Accessible Authentication (Minimum) (AA)
Authentication must not rely solely on cognitive function tests (such as memorizing passwords, solving math puzzles, or complex visual CAPTCHAs) without accessible alternatives (e.g., copy/paste support, password managers, or WebAuthn).
3.3.9 Accessible Authentication (Enhanced) (AAA)
Eliminates all cognitive tests and object recognition for authentication.
Applicability & Scope
- All forward-looking web applications, SaaS platforms, and digital public services aiming for state-of-the-art compliance.
TaggedWorks Engineering Role
We guide development teams through the technical implementation of WCAG 2.2 criteria, specializing in complex focus appearance, target size refactoring, and accessible authentication.
Ensure your digital platforms meet global accessibility standards.
Our senior accessibility engineers audit and remediate digital applications against WCAG, Section 508, EN 301 549, and PDF/UA, and document the test evidence.