GUIDE · UPDATED NOVEMBER 2026

WCAG 2.2: what’s new, the 6 new A/AA criteria, and how to check your site

WCAG 2.2 adds nine success criteria to WCAG 2.1 and retires one. Here is what changed, what each new Level A and AA criterion asks for, and how it relates to the ADA Title II rule.

The short version

PublishedOctober 2023, by the W3C Web Accessibility Initiative
Relationship to 2.1Builds on WCAG 2.1: a page that meets 2.2 also meets 2.1 (apart from the removed criterion below)
New success criteria9 in total: 2 at Level A, 4 at Level AA, 3 at Level AAA
Removed4.1.1 Parsing, which is obsolete in modern browsers
Required by ADA Title II?The DOJ rule names WCAG 2.1 Level AA, not 2.2. Meeting 2.2 AA goes beyond it and prepares you for later updates

General information, not legal advice. Check the current W3C text at w3.org/TR/WCAG22 and the legal requirements that apply to you before relying on this page.

The six new Level A and AA criteria

Most accessibility policies and laws target Level AA, so these six are the ones that matter in practice.

2.4.11 Focus Not Obscured (Minimum) — AA

When a keyboard user tabs to a control, it must not be completely hidden behind other content. The usual culprits are sticky headers, cookie banners and chat widgets. Check: tab through a long page and watch whether the focused link or button ever disappears under a fixed element.

2.5.7 Dragging Movements — AA

Anything that can be done by dragging, such as sliders, sortable lists and map panning, also needs a simple single-pointer alternative, like clicking buttons or tapping a target. Check: find every drag interaction and confirm there is a click or tap way to do the same thing.

2.5.8 Target Size (Minimum) — AA

Clickable targets should be at least 24 by 24 CSS pixels, unless there is enough spacing around smaller ones, the target is inline in a sentence, or the size is set by the browser. Check: look at icon buttons, close buttons, pagination and dense link lists.

3.2.6 Consistent Help — A

If you offer help, such as a contact link, chat or a phone number, it should appear in the same relative place on every page where it is offered. Check: compare the header and footer across page types.

3.3.7 Redundant Entry — A

Do not make people re-enter information they already gave in the same process, for example a shipping address repeated as a billing address, unless re-entry is essential for security. Check: walk through your multi-step forms and checkouts.

3.3.8 Accessible Authentication (Minimum) — AA

Logging in must not depend on a cognitive function test, such as remembering a password or solving a puzzle, unless an alternative exists. In practice this means allowing password managers and pasting into password fields, and offering options such as email links or passkeys. Check: try signing in using only a password manager and paste.

The three new Level AAA criteria

These are not required for most compliance targets, but they are worth knowing: 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance and 3.3.9 Accessible Authentication (Enhanced).

What was removed

Success criterion 4.1.1 Parsing was removed because browsers and assistive technology now handle markup errors consistently. Duplicate IDs and similar problems can still break accessibility, but they are now caught by other criteria such as 4.1.2 Name, Role, Value.

How WCAG 2.2 relates to the ADA Title II rule

The DOJ’s rule for state and local governments requires WCAG 2.1 Level AA. It does not require 2.2. Because 2.2 builds on 2.1, a site that meets 2.2 AA also meets the legal standard, and the six new criteria are cheap to fix at the same time as your 2.1 work. For deadlines and exemptions, see our guide to the ADA Title II web accessibility rule.

What automated scanning can and cannot check

Some of the new criteria can be tested automatically, such as target sizes and some focus behavior. Others, including Consistent Help, Redundant Entry and Accessible Authentication, depend on how a whole flow works and need a person to review them. An automated scan is the right place to start, not the end of the job.

Check your site with WCAGScan

WCAGScan checks your pages against WCAG 2.0, 2.1 and 2.2 and reports each issue with the criterion, the affected element and a suggested fix. The free scan covers up to 5 pages, with no account needed. See pricing.

Sources

See how your site measures up

Run a free scan