WCAG 2.2 AA: what to test and how to get there

What is WCAG 2.2 AA?

Think of it as a conformance target inside the current version of WCAG. To claim it, every full page and every step of a process must meet all Level A criteria and all Level AA criteria in version 2.2, plus the five conformance requirements. AAA criteria are not part of it.

Compared with the older 2.1 AA target, the list grows by six criteria and loses one. Six were added (four AA, two A), and 4.1.1 Parsing was taken out. Fifty minus one plus six gives the 55 criteria you test. If you are still deciding between versions, the WCAG 2.2 overview explains why the update happened.

The new rules in a WCAG 2.2 AA checklist

The table lists the six additions that sit at A or AA. Everything else on the AA list was already in 2.1, so if you passed a 2.1 AA audit recently, this is your gap list.

W3C explains each one in detail, for example Understanding target size (minimum). Three more criteria arrived at AAA (2.4.12, 2.4.13 and 3.3.9); they are optional for an AA target.

Code you will probably need

Two of the new rules are often fixed with a few lines of CSS. For sticky headers that hide focused links, tell the browser to leave room when it scrolls an item into view:

html {
  scroll-padding-top: 5rem;
}
.site-header {
  position: sticky;
  top: 0;
}

For icon buttons that are too small, set a minimum size on the clickable element itself, not just on the icon inside it:

<button class="icon-btn" aria-label="Close">
  <svg width="16" height="16" aria-hidden="true">...</svg>
</button>

.icon-btn {
  min-width: 24px;
  min-height: 24px;
}

For sign-in forms, use autocomplete="current-password" and never block paste on password or code fields, so password managers can do the remembering.

WCAG 2.2 level AA standards by principle

The 55 criteria are spread unevenly. Perceivable has the most AA items, mostly about contrast, zoom and media; Operable carries most of the new 2.2 work.

For the full list with tick boxes, use the interactive WCAG checklist with the level filter set to A and AA.

Who asks for WCAG 2.2 AA

The clearest requirement is in the UK: public sector websites and apps are monitored against WCAG 2.2 AA and must publish an accessibility statement. The gov.uk guidance sets out what is checked.

Elsewhere the change is happening through contracts. Many new tenders, vendor questionnaires and company policies now name 2.2 AA, or say “the latest version of WCAG at Level AA”. Laws that still cite WCAG 2.1 AA, such as EN 301 549, GIGW, SEBI's circular and the Title II rule in the US, are satisfied by 2.2 AA as well, so one target covers both.

Planning a move to WCAG 2.2 AA

If you already meet 2.1 AA, the upgrade is usually a short project. Work through it in this order:

1. Sticky and floating elements. Headers, cookie bars, chat launchers and sticky footers cause most 2.4.11 failures. Test them first.
2. Design system sizes. Set minimum sizes for icon buttons, tags, close buttons and pagination in the component library.
3. Drag interactions. Add a click alternative to each one. These need design time, so start early.
4. Login and verification. Remove paste blocking, review puzzle CAPTCHAs, and offer a method that needs no memory test.
5. Forms and help. Remove repeated questions in multi-step flows and fix the placement of help links.
6. Retest and update. Confirm with keyboard and touch, then update your accessibility statement to name 2.2 AA.

If you are starting from scratch, treat it like any AA project: templates first, key journeys next, and manual testing throughout. A WCAG checker can flag small targets, but it cannot judge dragging alternatives or login steps.

What WCAG 2.2 AA does not require

Two mix-ups come up in almost every project.

The second is focus styling. 2.4.13 Focus appearance, with its size and contrast formula, is AAA. At AA you need a visible focus indicator (2.4.7), enough contrast for it under non-text contrast, and focus that is not fully hidden (2.4.11).