Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 38 ยท Principles and WCAG

What WCAG 2.2 Added

A practical guide to the nine success criteria added in WCAG 2.2, covering focus, dragging, target size, consistent help, redundant entry and accessible authentication.

WCAG 2.2 became a W3C Recommendation in October 2023. It keeps everything from 2.1 and adds nine success criteria, mostly aimed at people with cognitive and motor disabilities and at touch users. Because many laws are moving to 2.2, knowing these criteria helps you stay ahead. This lesson explains each in plain language with code you can try.

Six are Level A or AA and affect everyday code; three are AAA. We list them all, then take the most important ones in detail.

The nine at a glance

Criterion Level One-line meaning
2.4.11 Focus Not Obscured (Minimum) AA The focused item is not completely hidden by sticky content
2.4.12 Focus Not Obscured (Enhanced) AAA No part of the focused item is hidden
2.4.13 Focus Appearance AAA Focus indicators are large and contrasting enough
2.5.7 Dragging Movements AA Anything done by dragging also has a single-pointer alternative
2.5.8 Target Size (Minimum) AA Pointer targets are at least 24 by 24 CSS pixels
3.2.6 Consistent Help A Help is in the same place across pages
3.3.7 Redundant Entry A Do not ask users to re-enter information already given
3.3.8 Accessible Authentication (Minimum) AA Login does not require a cognitive function test
3.3.9 Accessible Authentication (Enhanced) AAA Stricter version, no object recognition either

WCAG 2.2 at AA

Focus not hidden Sticky bars cannot cover focus
Drag alternative Buttons as well as dragging
Target size At least 24 by 24 pixels
Easy login Allow paste and managers

Plus consistent help and no redundant entry at Level A.

1 / 2

2.4.11 Focus Not Obscured

Sticky headers, cookie banners and chat widgets can sit on top of the element that has keyboard focus, so the user tabs and cannot see where they are. At AA the focused element must not be entirely hidden. The CSS fix is to reserve scroll space with scroll-padding-top equal to the height of the sticky header. You can see it below: tab through the links and watch the focused one scroll into view under or beside the bar.

Sticky header that respects focus

Remove the scroll-padding-top line and Tab backwards through the list: the focused link can slide under the header. With the rule, the browser scrolls it clear.

2.5.7 Dragging Movements

Drag-and-drop sorting, sliders and map panning are impossible for people who cannot hold and move a pointer, such as users of a head pointer or voice control. Provide a single-pointer alternative: up and down buttons, a number input, or click-to-place. Dragging may remain as an enhancement.

Reorder without dragging

2.5.8 Target Size (Minimum)

Small targets are hard to hit with a finger, a tremor or a trackpad. The AA rule asks for at least 24 by 24 CSS pixels, with exceptions: enough spacing around smaller targets, inline links in text, and controls whose size the browser sets. Aim for 44 by 44 where you can, which is the older AAA guideline and the usual mobile standard. A common fix is adding padding, or a pseudo-element, to enlarge the hit area while keeping the icon small.

3.2.6 Consistent Help and 3.3.7 Redundant Entry

If you provide help such as contact details, a chat link or a FAQ link, put it in the same relative position on every page. And do not make people type the same information twice in one process (for example a billing address that matches shipping): prefill it or offer a "same as shipping" checkbox. Exceptions include security needs and information that has expired.

3.3.8 Accessible Authentication

Logging in must not depend on a cognitive function test, such as remembering a password, solving a puzzle or transcribing characters, unless an alternative exists or a mechanism helps. Practically:

  • Let people paste into password fields and do not block password managers.
  • Use correct autocomplete="username" and autocomplete="current-password".
  • Offer email links, passkeys or OAuth sign-in as alternatives to hard-to-remember secrets.
A login form that helps

Paste works, a password manager can fill the correct fields, and a show-password toggle lowers the memory load. This is exactly what 3.3.8 asks for.

Focus appearance and the AAA extras

2.4.13 Focus Appearance describes the minimum area and contrast of a focus indicator, roughly a 2 CSS pixel outline with 3:1 contrast against its surroundings. You will see it in the focus styles lesson. 2.4.12 and 3.3.9 are AAA, so you can adopt them selectively.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the minimum target size required at Level AA in WCAG 2.2?

    2.5.8 sets 24 by 24 CSS pixels, with exceptions for spacing, inline links and user-agent controls.
  2. 2. A sortable list works only by drag and drop. What does WCAG 2.2 require?

    2.5.7 asks for an alternative that does not need dragging unless dragging is essential.
  3. 3. Which CSS property helps stop sticky headers from hiding focused elements?

    scroll-padding keeps room at the edge so the browser scrolls focused items clear of the sticky bar.
  4. 4. Which is a good practice for Accessible Authentication?

    Password managers and paste lessen the memory load, which is the point of 3.3.8.

Summary

  • WCAG 2.2 adds nine criteria, six at Level A or AA and three at AAA.
  • Keep focus visible under sticky UI, offer non-drag alternatives and make targets at least 24 by 24 pixels.
  • Keep help in the same place and never ask for the same information twice.
  • Support password managers, paste and passwordless login.

Next: Landmarks and Page Regions