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

WCAG 2.2 became a W3C Recommendation in October 2023, and it raises a fair question for anyone chasing compliance: which version do I actually have to meet, and how different is the newer one? The short version — the law still points at 2.1, but 2.2 is where accessibility is heading, and building to it now is straightforward.

Quick answer: WCAG 2.2 adds nine new success criteria to 2.1 and removes one obsolete criterion (4.1.1 Parsing). Six of the additions are at Level A or AA — the legally relevant levels — covering focus visibility, dragging alternatives, minimum target size, consistent help, redundant entry, and accessible authentication. WCAG 2.2 is backward compatible: meeting 2.2 AA means you also meet 2.1 AA. The ADA Title II rule currently references WCAG 2.1 AA, so that is the binding legal target today — but 2.2 is the direction of travel, and its new criteria are common-sense fixes worth adopting now.

A quick version history

WCAG 2.0 arrived in 2008 and is still the benchmark Section 508 cites. WCAG 2.1 (2018) added 17 criteria, mostly for mobile, low vision, and cognitive accessibility — and it is the version the ADA Title II rule adopts. WCAG 2.2 (2023) is the latest, adding nine more criteria that reflect what a decade of real-world testing revealed. Each version is additive: 2.2 contains everything in 2.1, which contains everything in 2.0.

The new Level A and AA criteria in 2.2

These six are the ones that matter for legal conformance:

2.4.11 Focus Not Obscured (Minimum) – AA: when an element receives keyboard focus, it can't be completely hidden behind a sticky header, cookie banner, or chat widget.
2.5.7 Dragging Movements – AA: anything you operate by dragging (sliders, drag-and-drop) must also work with a simple tap or click, for users who can't drag precisely.
2.5.8 Target Size (Minimum) – AA: interactive targets must be at least 24×24 CSS pixels (with spacing exceptions), so buttons and links aren't too small to hit reliably.
3.2.6 Consistent Help – A: if you offer help (a contact link, phone number, chat), it appears in a consistent place across pages.
3.3.7 Redundant Entry – A: don't force users to re-enter information they already provided in the same process — auto-populate or let them select it.
3.3.8 Accessible Authentication (Minimum) – AA: login can't depend on a cognitive test like remembering a password or solving a puzzle CAPTCHA without an accessible alternative (e.g., allow password managers, offer email links).

The one removal: 4.1.1 Parsing

WCAG 2.2 formally removes success criterion 4.1.1 (Parsing), which required valid HTML parsing. Modern browsers and assistive technologies handle malformed markup gracefully, so the criterion no longer reflected real barriers. It is marked as always satisfied — you don't need to test for it anymore.

Not sure whether your site clears 2.1 AA, let alone 2.2? We audit against the exact success criteria that apply to you and hand you a prioritized, documented remediation plan.

Get a Section 508 remediation quote →

Which version do you legally have to meet?

Today, the binding standards point at 2.1 AA (ADA Title II) or 2.0 AA (Section 508). No U.S. regulation yet mandates 2.2. So if you are racing a deadline, 2.1 AA is the requirement — do not let “but there's a 2.2 now” distract you from clearing the criteria you are actually measured against.

Why build to 2.2 anyway

Two reasons. First, the 2.2 additions are cheap, sensible fixes — bigger tap targets, help in a consistent spot, login that doesn't punish people — that improve the experience for everyone, not just users with disabilities. Second, standards only move forward; the next time a regulation updates, it will reference 2.2 (or later). Building to 2.2 AA now means you satisfy every current legal requirement and you are ready for the next one, with no rework. Since 2.2 is backward compatible, there is no downside to aiming a little higher.