SiteBrace

All Learn articles » WCAG 2.2 vs 2.1

WCAG 2.2 vs 2.1: when to upgrade and what's actually new

WCAG 2.2 became a W3C Recommendation in October 2023, adding 9 new success criteria on top of WCAG 2.1 (and removing one). Most US legal references, including the DOJ's April 2024 Title II web rule, still cite WCAG 2.1 Level AA as the conformance standard. So when should you actually upgrade your conformance target to 2.2? Here's the practical answer.

Status of each version (as of 2026)

  • WCAG 2.0: December 2008 W3C Recommendation. Still legally referenced in older laws and contracts.
  • WCAG 2.1: June 2018 W3C Recommendation. The standard cited in the DOJ Title II April 2024 web rule, in Section 508 (US federal procurement, refresh), and in the European EN 301 549 standard.
  • WCAG 2.2: October 2023 W3C Recommendation. Adopted by some private organizations as their conformance target; not yet the cited standard in most US legal references.
  • WCAG 3.0: Working draft. Not a Recommendation. Years away from being ready as a conformance target.

Each version is fully backward-compatible: a page that conforms to WCAG 2.2 also conforms to 2.1 and 2.0 (with one exception, see below). So upgrading the target is purely additive, never a regression.

What's new in WCAG 2.2

9 new success criteria across the four WCAG principles. Each one addresses a real-world accessibility issue that wasn't well-covered in 2.1. Plain-English descriptions:

Level A additions (1)

  • 3.2.6 Consistent Help. If your site offers help (a contact link, a chat widget, a help phone number) on multiple pages, it must appear in the same relative order across pages. Prevents users from re-learning where help lives on every page.

Level AA additions (5)

  • 2.4.11 Focus Not Obscured (Minimum). When a UI element receives keyboard focus, the focused element must not be entirely hidden behind a sticky header, cookie banner, or other overlay. At least part of it must be visible. This is the criterion most likely to fail on modern sites with sticky elements.
  • 2.5.7 Dragging Movements. Any function that uses dragging (signature pads, sortable lists, range sliders) must have an alternative single-pointer method (typing, button taps). Drag-only interactions exclude users with motor impairments.
  • 2.5.8 Target Size (Minimum). Interactive targets (buttons, links) must be at least 24 by 24 CSS pixels, with some exceptions for inline targets in flowing text. This is roughly half the size of the 2.5.5 (AAA) target-size criterion in WCAG 2.1.
  • 3.3.7 Redundant Entry. If a multi-step form asks for the same information twice (shipping address that's also the billing address), the second instance must be auto-populated or selectable. Eliminates retyping for users with cognitive or motor impairments.
  • 3.3.8 Accessible Authentication (Minimum). Authentication cannot rely solely on a cognitive function test (remembering a password, solving a puzzle, transcribing characters). Must offer an alternative such as biometric, hardware token, or paste-from-password-manager. Ironically, this is the criterion most likely to push sites toward password managers and SSO.

Level AAA additions (3)

Less commonly targeted by SMBs (Level AAA is rarely the conformance target):

  • 2.4.12 Focus Not Obscured (Enhanced). Stricter version of 2.4.11; focused elements must be entirely visible.
  • 2.4.13 Focus Appearance. Specifies minimum visual focus indicator characteristics (contrast, size).
  • 3.3.9 Accessible Authentication (Enhanced). Stricter version of 3.3.8; cannot rely on object recognition either.

The one removed criterion

  • 4.1.1 Parsing (was in 2.0 and 2.1, removed in 2.2). Required that HTML parse without certain validation errors. Removed because modern browsers handle parsing errors gracefully and the criterion was no longer providing user-facing accessibility benefit.

When should you target 2.2 instead of 2.1?

Reasons to stay on WCAG 2.1 AA as your conformance target

  • You are a state or local government entity covered by the April 2024 DOJ Title II web rule. The rule cites WCAG 2.1 AA. Conforming to 2.1 AA satisfies the rule; conforming to 2.2 AA also satisfies the rule (because 2.2 is a superset), but you only need 2.1 AA.
  • You sell to government, and the procurement language in your contracts refers to WCAG 2.1 AA or "WCAG 2.1 Level AA or later." Match the contract.
  • Your accessibility budget is finite and you are pre-remediation. Get 2.1 AA clean first; layer in 2.2 additions afterward.

Reasons to upgrade to WCAG 2.2 AA

  • You are a private business in a competitive market where accessibility is a differentiator (healthcare, education software, fintech). 2.2 conformance signals you are ahead of the regulatory curve.
  • You are a contractor and your customer's RFP or procurement clause cites "WCAG 2.2 AA or later." Match the contract.
  • Your site already passes most of 2.1, the additional 5 AA criteria are easy to add (sticky-header focus, drag alternatives, target-size minimum), and you want a forward-looking conformance statement.
  • You operate in the EU. EN 301 549, the European accessibility standard, is being updated to reference WCAG 2.2 in upcoming revisions. Upgrading now keeps you ahead of EU procurement language.

Practical recommendation for SMBs

If you are doing your first audit and you are not sure which target to pick, start with WCAG 2.1 AA. Reasons:

  1. It is the standard the DOJ cites, the standard most automated tools default to, and the standard most procurement language references.
  2. It contains 50 success criteria; 2.2 adds 9 more (5 at AA). The 50-criteria target is a substantial first effort.
  3. Achieving 2.1 AA puts you in a strong position to add the 5 additional 2.2 AA criteria in a follow-up cycle.

Site Brace audits test against WCAG 2.1 AA by default. If you specifically need a 2.2 audit, the axe-core engine we use supports 2.2 rule tags, and we can configure the audit to test 2.2 on request; tell us when you submit your intake.

What about WCAG 3.0?

WCAG 3.0 is in working-draft status at the W3C and represents a significant rework of the framework: numerical scoring, broader coverage, different conformance model. It is years away from being a stable Recommendation, and even longer from being the cited standard in any law. Do not target WCAG 3.0 today; it is not stable enough. Watch the W3C accessibility-guidelines-working-group for updates.

Start a Site Brace audit, $149