W3C Published September 2023 · 9 New Success Criteria

WCAG 2.1 vs WCAG 2.2: What Changed and Why It Matters

WCAG 2.2 was published in September 2023, adding 9 new accessibility success criteria focused on mobile usability and cognitive accessibility. Here's exactly what changed, what's now required, and whether your existing audit needs to be updated.

TL;DR
  • WCAG 2.2 was published by the W3C on September 5, 2023 — it is the current standard.
  • WCAG 2.2 adds 9 new success criteria and removes 1 (4.1.1 Parsing).
  • All WCAG 2.1 Level A and AA criteria still apply in WCAG 2.2.
  • New criteria focus on: touch target sizes, focus visibility, cognitive accessibility, and authentication.
  • The DOJ April 2024 rule mandates WCAG 2.1 AA for government; WCAG 2.2 AA is best practice for private businesses.
  • complyTech audits to WCAG 2.2 Level AA — the highest defensible standard as of 2025.

What Is WCAG?

WCAG (Web Content Accessibility Guidelines) is the technical standard for web accessibility developed by the World Wide Web Consortium (W3C). It is organized into three conformance levels: A (minimum), AA (standard), and AAA (enhanced). ADA Title III courts use WCAG Level AA as the benchmark for measuring website compliance.

WCAG 2.1 vs WCAG 2.2 — Side-by-Side Comparison

FeatureWCAG 2.1WCAG 2.2
PublishedJune 2018September 5, 2023
Total Success Criteria7886 (net 87 total, –1 removed, +9 new)
Level A Criteria3032 (+2 new)
Level AA Criteria2024 (+4 new at AA)
Level AAA Criteria2830 (+3 new at AAA)
New Focus AreasMobile, low visionCognitive, motor, mobile UX
Removed CriteriaNone4.1.1 Parsing (no longer needed)
DOJ MandateGovernment: April 2024 ruleNot yet mandated (current best practice)
ADA Court StandardMinimum legal benchmarkBest practice — future-proof defense

The 9 New WCAG 2.2 Success Criteria — Explained

These are the criteria that appear in WCAG 2.2 but not in WCAG 2.1. If your last audit was against WCAG 2.1, your site has not been tested for any of these:

2.4.11 Focus Not Obscured (Min) AA

What it requires: Focused components must not be entirely hidden by sticky headers, footers, or other elements.

Sticky navigation and chat widgets covering focused elements fail this criterion.

2.4.12 Focus Not Obscured (Enhanced) AAA

What it requires: Focused component must be fully visible — no portion hidden.

AAA — not required for minimum compliance but best practice.

2.4.13 Focus Appearance AAA

What it requires: The focus indicator must meet minimum contrast and size requirements.

AAA level — addresses thin or low-contrast default focus rings.

2.5.7 Dragging Movements AA

What it requires: Functionality using drag-and-drop must have a single-pointer alternative.

Drag-to-reorder lists, sliders operated by dragging, and similar interactions need pointer alternatives.

2.5.8 Target Size (Minimum) AA

What it requires: Touch/click targets must be at least 24×24 CSS pixels.

Small icon buttons, close X buttons, and inline link text often fail this on mobile.

3.2.6 Consistent Help A

What it requires: Help mechanisms (chat, phone, contact link) must appear consistently across pages.

Help buttons that appear on some pages but not others violate this criterion.

3.3.7 Redundant Entry A

What it requires: Users should not need to re-enter information already provided in the same process.

Multi-step forms that ask for the same info (email, address) twice fail this criterion.

3.3.8 Accessible Authentication (Min) AA

What it requires: Authentication must not require cognitive tests (CAPTCHA) without alternatives.

Image CAPTCHAs and puzzle CAPTCHAs fail this unless audio or alternative is provided.

3.3.9 Accessible Authentication (Enh) AAA

What it requires: Authentication must not rely on cognitive function tests at all.

AAA level — full CAPTCHA removal required for AAA conformance.

What Was Removed: 4.1.1 Parsing

WCAG 2.2 removes Success Criterion 4.1.1 (Parsing), which required valid HTML markup free of parsing errors. This criterion was removed because modern browsers have become robust enough to handle HTML parsing inconsistencies consistently — the original purpose of 4.1.1 is now addressed by browser normalization behavior.

Legal Status in 2025: Which Standard Is Required?

  • Government websites (state/local): WCAG 2.1 Level AA mandated by DOJ final rule, April 2024
  • Federal programs (Section 508): W3C WCAG 2.0 Level AA remains the formal reference, but agencies increasingly adopt 2.1
  • Private businesses (ADA Title III): Courts apply WCAG 2.1 AA as the minimum standard; WCAG 2.2 AA is best practice

complyTech audits all clients to WCAG 2.2 Level AA — the current published standard. This provides the broadest legal protection and ensures your site meets both current and anticipated future enforcement standards.

Frequently Asked Questions

WCAG 2.2, published by the W3C in September 2023, adds 9 new success criteria beyond WCAG 2.1, focusing on mobile usability and cognitive accessibility. It also removes Success Criterion 4.1.1 (Parsing), which browsers now handle consistently. All other WCAG 2.1 Level A and AA criteria still apply in WCAG 2.2. The new criteria address minimum touch target sizes, focus visibility, accessible authentication, and consistent help mechanisms.

The DOJ's April 2024 final rule specifies WCAG 2.1 Level AA for state/local government websites. For private businesses under ADA Title III, courts use WCAG 2.1 AA as the minimum legal benchmark. However, complyTech recommends auditing to WCAG 2.2 Level AA — providing broader coverage, better protection against future legal claims, and genuinely better accessibility for real users.

If your site was previously audited to WCAG 2.1 Level AA, it meets current minimum legal requirements. However, a WCAG 2.2 gap audit is recommended to address the 9 new criteria — particularly important if your site has significant mobile traffic or serves users with cognitive disabilities. A gap audit is less expensive than a full audit and focuses only on the new 2.2 criteria.

WCAG 2.5.8 requires that interactive elements (buttons, links, form controls) have a click/touch target size of at least 24×24 CSS pixels. This is especially important for mobile users and users with motor impairments who struggle to precisely tap small elements. Existing elements that don't meet this size requirement fail WCAG 2.2 Level AA.

WCAG 3.3.8 requires that authentication processes (login, CAPTCHA) do not rely on cognitive tests — like solving puzzles, transcribing text, or recognizing images — unless an accessible alternative is provided. This directly addresses CAPTCHAs that use image recognition or distorted text, which are inaccessible to many users with cognitive or visual disabilities.

Audit Your Website to WCAG 2.2 Level AA

complyTech audits to WCAG 2.2 — 9 criteria beyond what a WCAG 2.1 audit covers. Future-proof your compliance with the current published standard and a defensible legal record.

Response within 1 business day
IAAP-certified audit team
No obligation — includes scope & pricing
Compliance certificate post-remediation