WCAG 2.2 vs WCAG 2.1: What Changed and What It Means for Your Business

The W3C published WCAG 2.2 in October 2023, introducing 9 new success criteria and removing one. If your organization built its accessibility program around WCAG 2.1 AA — the standard referenced in most ADA demand letters and Section 508 policy — you need to understand what changed and whether your current conformance claims hold up.

What got added in WCAG 2.2

WCAG 2.2 adds new criteria across focus management, dragging operations, and authentication. Here are the most important ones for most organizations:

• 2.4.11 Focus Not Obscured (Minimum) — A focused component must not be entirely hidden by author-created content (e.g., a sticky header covering the focused element).
• 2.4.12 Focus Not Obscured (Enhanced) — Stricter version: no part of the focused component should be hidden.
• 2.4.13 Focus Appearance — Focused UI components must have a focus indicator of sufficient size and contrast.
• 2.5.7 Dragging Movements — Any action that uses a dragging motion must be achievable with a single pointer (no drag required).
• 2.5.8 Target Size (Minimum) — Interactive targets must be at least 24x24 CSS pixels.
• 3.2.6 Consistent Help — Help mechanisms (chat, phone, FAQ) must appear in the same order across pages.
• 3.3.7 Redundant Entry — Information already entered by the user must not be asked again in the same session.
• 3.3.8 Accessible Authentication (Minimum) — Cognitive function tests (like CAPTCHAs) must have an alternative.

What got removed

Success Criterion 4.1.1 Parsing was removed in WCAG 2.2. This criterion required well-formed HTML markup and was originally included because assistive technologies relied on parsing raw HTML. Modern browsers and screen readers handle malformed HTML gracefully, making this criterion obsolete. If you had passing audits partly due to 4.1.1, nothing changes — its removal tightens the standard, it does not loosen it.

Do you need to update now?

Most ADA demand letters and Department of Justice guidance still reference WCAG 2.1 AA as the benchmark. Section 508 has not yet formally adopted WCAG 2.2. However, the ICT Testing Baseline and many enterprise procurement requirements are moving toward 2.2. Our recommendation:

• If you are doing a net-new audit: target WCAG 2.2 AA from the start.
• If you have an existing WCAG 2.1 AA conformance claim: plan a gap assessment against 2.2 in the next 6 months.
• Focus first on focus appearance (2.4.13) and target size (2.5.8) — these are the most commonly failed new criteria.

The bottom line

WCAG 2.2 is not a dramatic overhaul — it refines and strengthens 2.1. Organizations that were genuinely compliant with 2.1 AA will find most of the new criteria already covered. The new criteria around focus indicators and target sizes are where most existing sites will find gaps. These are also the criteria that most directly affect keyboard and switch-access users — the populations that most need your site to work.