Skip to main content
Raasta

Guide · reviewed 5 November 2026

WCAG 2.2 explained: the nine new success criteria

WCAG 2.2 became a W3C Recommendation on 5 October 2023. It keeps every WCAG 2.1 criterion except 4.1.1 Parsing, which was removed, and adds nine new success criteria: six at levels A and AA, three at AAA. If your site meets WCAG 2.2 AA, it also meets WCAG 2.1 AA.

Level AANeeds a person to check

2.4.11 Focus Not Obscured (Minimum)

When an element gets keyboard focus, it must not be completely hidden by something the site put on top of it, such as a sticky header, cookie banner or chat button.

Who it helps: Keyboard users and people using switch devices, who need to see where they are on the page.

What to do

  • Give sticky headers and footers room with scroll-padding-top / scroll-padding-bottom on the html element, so focused items scroll clear of them.
  • Make cookie banners and chat widgets dismissible, and don’t let them cover form fields or links.

Level AAANeeds a person to check

2.4.12 Focus Not Obscured (Enhanced)

The stricter version of 2.4.11: no part of the focused element may be hidden by content the site added.

Who it helps: The same people as 2.4.11, with a stronger guarantee.

What to do

  • The same techniques as 2.4.11, applied so the whole focused element stays visible.

Level AAANeeds a person to check

2.4.13 Focus Appearance

The focus indicator must be at least as large as a 2 CSS pixel outline around the element, and change contrast by at least 3:1 between focused and unfocused states.

Who it helps: Keyboard users with low vision, who can miss a faint or thin focus ring.

What to do

  • Use a solid outline of 2px or more with an offset, for example outline: 2px solid currentColor; outline-offset: 2px on :focus-visible.
  • Never remove the outline without putting a clearly visible replacement in its place.

Level AANeeds a person to check

2.5.7 Dragging Movements

Anything done by dragging (sliders, sortable lists, maps, kanban cards) must also be possible with single clicks or taps, unless dragging is essential.

Who it helps: People with tremors or limited dexterity, and people using a head pointer, eye tracking or voice control.

What to do

  • Add up/down or “move to” buttons to sortable lists and boards.
  • Let sliders accept a click on the track, arrow keys and a number input.

Level AAPartly checked by automated scans

2.5.8 Target Size (Minimum)

Click and tap targets must be at least 24 × 24 CSS pixels, or have enough space around them, with a few exceptions such as links inside a sentence.

Who it helps: People with tremors or limited dexterity, and anyone using a phone one-handed.

What to do

  • Give icon buttons a min-width and min-height of 24px (44px is better for touch).
  • Space small adjacent targets so a 24px circle centred on each one doesn’t overlap another target.

Fix guide with code: target size (minimum)

Level ANeeds a person to check

3.2.6 Consistent Help

If a site offers help (contact details, a contact form, a chat, an FAQ) on several pages, it must appear in the same relative place on each of them.

Who it helps: People with cognitive or learning disabilities, who rely on finding help where they found it before.

What to do

  • Put the help link or contact details in a shared header or footer, in the same order on every page.

Level ANeeds a person to check

3.3.7 Redundant Entry

In a multi-step process, information the user already entered must be filled in for them or offered to select, instead of asked for again, unless re-entry is essential or needed for security.

Who it helps: People with cognitive or memory disabilities, and people for whom typing is slow or painful.

What to do

  • Offer “Billing address same as delivery” in checkouts.
  • Carry answers forward between the steps of a form instead of asking again.

Level AANeeds a person to check

3.3.8 Accessible Authentication (Minimum)

Logging in must not depend on a cognitive function test, such as remembering a password or solving a puzzle, unless there is an alternative or help such as a password manager or copy and paste.

Who it helps: People with cognitive disabilities, dyslexia or memory loss.

What to do

  • Let password managers fill the form: use autocomplete="username" and autocomplete="current-password", and never block paste.
  • Offer an email magic link or passkeys as an alternative to a password.
  • If you use a CAPTCHA, prefer one that needs no puzzle, or offer another way through.

Level AAANeeds a person to check

3.3.9 Accessible Authentication (Enhanced)

The stricter version of 3.3.8: it also rules out recognising objects or personal content (for example “pick the photos with a bus”) as the only way in.

Who it helps: The same people as 3.3.8.

What to do

  • Offer a login path with no test at all, such as a magic link or a passkey.

Removed: 4.1.1 Parsing

Removed in WCAG 2.2 because modern browsers and assistive technologies no longer depend on perfectly valid HTML. For WCAG 2.1, W3C notes it is always considered satisfied.

Questions

When was WCAG 2.2 published?

WCAG 2.2 became a W3C Recommendation on 5 October 2023. It is the current version of the Web Content Accessibility Guidelines.

What is new in WCAG 2.2?

Nine new success criteria: Focus Not Obscured (Minimum and Enhanced), Focus Appearance, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum and Enhanced). Criterion 4.1.1 Parsing was removed.

Which WCAG 2.2 criteria are level AA?

Four new criteria are level AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum) and 3.3.8 Accessible Authentication (Minimum). Two are level A: 3.2.6 Consistent Help and 3.3.7 Redundant Entry. A site that conforms at AA must meet all six.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds nine success criteria to WCAG 2.1 and removes 4.1.1 Parsing. Everything else is the same, so content that meets WCAG 2.2 also meets WCAG 2.1 at the same level.

Does the European Accessibility Act require WCAG 2.2?

The EAA names no WCAG version. Conformity is shown through the harmonised standard EN 301 549, whose web requirements are WCAG 2.1 Level AA. WCAG 2.2 AA includes all of 2.1 AA, so meeting 2.2 AA covers both.

Can an automated scanner check WCAG 2.2?

Only partly. Target size can be measured automatically; the other new criteria need a person to try the page with a keyboard, a login form or a multi-step process. Automated checks find a large share of problems overall, not all.

Check a page against the automated WCAG 2.2 rules with the free Raasta scan, then test the criteria above that need a person. Next: read the European Accessibility Act guide, write an accessibility statement, or see the most common automated failures and their fixes.

Sources