WCAG 2.2: What Changed and Why It Matters for Auditors

WCAG 2.2 became a W3C Recommendation in October 2023. For most teams, the update arrived quietly, but for accessibility auditors, it changed the checklist in meaningful ways. Nine new success criteria were introduced, one was deprecated, and the overall focus shifted toward better support for users with cognitive disabilities and those navigating on mobile or touch devices.

Here is what you need to know.

The 9 New Success Criteria

Focus Appearance (2.4.11 - AA, 2.4.13 - AAA)

Two criteria replace and extend the older focus visible requirement. The AA criterion (2.4.11) requires that the focus indicator meet minimum size and contrast thresholds. The AAA version (2.4.13) raises the bar further. In practice, this means auditors now need to measure focus ring dimensions and contrast ratios, not just verify that a focus indicator exists.

Focus Not Obscured (2.4.12 - AA, 2.4.13 - AAA)

Sticky headers and chat widgets are common culprits here. The AA criterion requires that a focused component is not entirely hidden behind other content. The AAA version requires it to be fully visible. When auditing, scroll through pages with fixed or sticky elements and tab through interactive components to check.

Dragging Movements (2.5.7 - AA)

Any functionality that requires dragging must also be achievable through a single pointer action without a drag. This affects sliders, sortable lists, map panning, and similar interactions. Auditors should specifically test drag-only interfaces with a mouse and verify that an equivalent non-drag path exists.

Target Size (2.5.8 - AA)

Interactive targets must be at least 24x24 CSS pixels, or have adequate spacing so that the 24x24 area around the target does not intersect adjacent targets. This is a relaxed but still meaningful upgrade from the AAA criterion in 2.1. Inline text links are exempt, which auditors should note when reviewing dense navigation or tag lists.

Consistent Help (3.2.6, A)

If a page includes a help mechanism, such as a contact link, phone number, or chat button, it must appear in a consistent location across pages. This is straightforward to check: navigate between pages and confirm help entry points appear in the same relative position.

Accessible Authentication (3.3.7, A, 3.3.8 - AA)

Cognitive tests must not be required during authentication unless an alternative is provided. This includes CAPTCHAs and memory-based challenges. The AA version prohibits cognitive function tests entirely unless a mechanism exists to bypass or assist with them. Auditors should walk through every login, registration, and password-reset flow.

Redundant Entry (3.3.7, A)

Information already provided by the user in the same session must not be requested again, unless re-entering is essential, for security reasons, or the earlier data is no longer valid. Multi-step forms and checkout flows are the primary targets here.

What Was Deprecated: 4.1.1 Parsing

Success Criterion 4.1.1 (Parsing) has been deprecated in WCAG 2.2. Modern browsers and assistive technologies handle many historical parsing errors gracefully, making this criterion largely redundant. Auditors using automated tools will still see it flagged, but it should not count against a compliance score. Update your audit templates accordingly.

What This Means for Auditors in Practice

The changes in WCAG 2.2 require both new test procedures and some updates to existing ones:

• Update your checklist: Add the 9 new SCs and mark 4.1.1 as deprecated or removed from scoring.
• Add visual measurement steps: Focus Appearance (2.4.11) requires checking pixel dimensions and contrast, consider tooling that can assist with this.
• Expand interaction testing: Dragging Movements and Target Size require hands-on interaction testing that automated scanners cannot fully cover.
• Review sticky UI patterns: Many products use fixed headers, cookie banners, and chat overlays. Focus Not Obscured is frequently violated without teams realising it.
• Walk through auth flows thoroughly: Accessible Authentication affects a critical part of the user journey and is often overlooked.

Quick Tips for Updating Your Audit Checklists

1. Download or fork the latest WCAG 2.2 Quick Reference and use it as your base document.
2. Group the new SCs by the type of testing they require: visual measurement, interaction testing, form review.
3. Mark 4.1.1 explicitly in your templates with a note explaining the deprecation, so clients and stakeholders are not confused when they see it missing from results.
4. If you use an audit tool like CheckFox, verify that the SC list has been updated to reflect 2.2 and that deprecated criteria are handled correctly in scoring.

WCAG 2.2 is not a revolution, but it closes real gaps that affected users with cognitive disabilities and touch device users every day. Updating your audit practice now means more accurate results, better coverage, and audit reports that reflect the current standard.