WCAG 2.2
WCAG 2.2 was published by the W3C in October 2023. It builds on WCAG 2.1 by adding 9 new success criteria focused on cognitive accessibility, mobile usability, and improved focus visibility — while removing one outdated criterion.
What's New in WCAG 2.2
WCAG 2.2 introduces 9 new success criteria across three focus areas:
Focus Visibility
Stronger requirements for keyboard focus indicators to be clearly visible.
Mobile & Pointer
Minimum target sizes and alternatives to dragging gestures.
Cognitive Accessibility
Consistent help, redundant entry prevention, and accessible authentication.
New Success Criteria
Focus Appearance (Minimum)
When a keyboard focus indicator is visible, it must have a minimum area and contrast ratio. The focus indicator must have a perimeter of at least the CSS outline of 2 CSS pixels and a contrast ratio of at least 3:1 between focused and unfocused states.
Focus Appearance (Enhanced)
The keyboard focus indicator must have an area of at least the CSS outline of 2 CSS pixels around the component, and a contrast ratio of at least 4.5:1 between focused and unfocused states.
Focus Appearance
When a keyboard focus indicator is visible, it must have sufficient size and contrast so users can clearly see which element has focus. Replaces 2.4.11 in the final WCAG 2.2 specification.
Dragging Movements
All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the function is determined by the user agent and not modified by the author.
Target Size (Minimum)
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where the target offset is at least 24px, the target is inline, or the size is determined by the user agent and not modified by the author.
Consistent Help
If a web page provides any of the following help mechanisms — human contact details, human contact mechanism, self-help option, or a fully automated contact mechanism — and those mechanisms are repeated on multiple pages, they occur in the same relative order on each page.
Redundant Entry
Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select, except where re-entering the information is essential, the information is required for security purposes, or the previously entered information is no longer valid.
Accessible Authentication (Minimum)
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one alternative method, a mechanism to assist the user, or the cognitive function test is to recognize objects or personal content.
Accessible Authentication (Enhanced)
A cognitive function test is not required for any step in an authentication process unless that step provides an alternative that does not rely on a cognitive function test.
Removed Criterion
WCAG 2.2 removes one criterion from WCAG 2.1:
Parsing
RemovedModern browsers handle parsing errors consistently; this criterion is no longer meaningful in practice.
Conformance Levels
| Level | Description | New in 2.2 |
|---|---|---|
| A | Minimum accessibility. Must be met. | 3.2.6 Consistent Help, 3.3.7 Redundant Entry |
| AA | Standard compliance target for most regulations. | 2.4.11/2.4.13 Focus Appearance, 2.5.7 Dragging, 2.5.8 Target Size, 3.3.8 Auth |
| AAA | Highest level. Recommended where possible. | 2.4.12 Focus Appearance Enhanced, 3.3.9 Auth Enhanced |
ConformPilot & WCAG 2.2
ConformPilot supports WCAG 2.2 auditing across all three conformance levels. When you select WCAG 2.2 AA as your standard, the audit engine checks all applicable success criteria including the new 2.2 additions.
- ✓ Automated checks for focus appearance and target size
- ✓ Dragging movement alternative detection
- ✓ Authentication flow analysis
- ✓ VPAT reports mapped to WCAG 2.2 criteria
- ⚠ Some criteria (Redundant Entry, Consistent Help) require manual review