Sprout
en
Language English en Español es Region: Europe · EUR €
Sprout
All posts
Accessibility

WCAG 2.2 AA checklist: all 55 criteria explained

Profile of the author

Jonathan Bell

Co-founder, Sprout ·

Quick answer

To meet WCAG 2.2 AA, a website must satisfy every Level A and Level AA success criterion that applies to it: 55 in total, 31 at Level A and 24 at Level AA. The criteria marked AA aren’t enough on their own. Below are all 55 in tables, with what each one requires, how to test it and how much an automated scan can catch.

What’s new in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on 5 October 2023. It adds nine success criteria to WCAG 2.1 and removes 4.1.1 Parsing as obsolete. Six of the new criteria are Level A or AA, so they’re part of this checklist:

  • 2.4.11 Focus Not Obscured (Minimum), AA
  • 2.5.7 Dragging Movements, AA
  • 2.5.8 Target Size (Minimum), AA
  • 3.2.6 Consistent Help, A
  • 3.3.7 Redundant Entry, A
  • 3.3.8 Accessible Authentication (Minimum), AA

The other three (2.4.12, 2.4.13 and 3.3.9) are AAA. If your site already met WCAG 2.1 AA, check these six first.

WCAG 2.2 and the European Accessibility Act

The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025, through each member state’s national law. For technical conformity, the European reference is the standard EN 301 549. Version 3.2.1 points to WCAG 2.1 AA. ETSI published version 4.1.1 on 2 September 2026, which updates that reference to WCAG 2.2. It takes full legal effect once it’s cited in the Official Journal of the EU.

In practice: if you’re starting accessibility work today, aim for WCAG 2.2 AA. Whether the EAA applies to you depends on the products and services you offer, and on the national law where you operate.

How to use this checklist

  1. Scan first, to find the failures a tool can detect on its own.
  2. Group by component and template. A failure in the menu repeats on every page.
  3. Test complete journeys: checkout, sign-up, search, log-in.
  4. For each criterion, record how you tested it and what you found.
  5. Repeat after every significant change.

The “Auto” column is Sprout’s own rating, not the W3C’s. High: software can check almost all of it. Partial: a tool finds signals, but a person has to judge. Low: it depends on interaction or meaning.

Principle 1. Perceivable: 20 criteria

CriterionLevelWhat it requiresHow to test itAuto
1.1.1 Non-text ContentAAn equivalent text alternative for images, icons and charts that carry informationUse a screen reader: does the alt text describe the purpose or content?Partial
1.2.1 Audio-only and Video-only (Prerecorded)AA transcript or equivalent alternativeReview each media fileLow
1.2.2 Captions (Prerecorded)ASynchronised captionsPlay the video with the sound offLow
1.2.3 Audio Description or Media Alternative (Prerecorded)AAn alternative for information that’s only visualListen to the video without watchingLow
1.2.4 Captions (Live)AACaptions for live broadcastsWatch live streams and webinars without soundLow
1.2.5 Audio Description (Prerecorded)AAAudio description of the relevant visual informationListen without watching: are actions or on-screen text missing?Low
1.3.1 Info and RelationshipsAHeadings, lists, tables and labels marked up in the code, not just styledInspect the semantics and test with a screen readerPartial
1.3.2 Meaningful SequenceAThe code order keeps the meaningCompare the visual order with the DOM orderPartial
1.3.3 Sensory CharacteristicsAInstructions don’t rely only on shape, size, position or soundLook for text like “press the round button on the right”Partial
1.3.4 OrientationAADon’t lock the view to portrait or landscapeRotate the devicePartial
1.3.5 Identify Input PurposeAACorrect autocomplete attribute on personal-data fieldsCheck name, email, address and phone fieldsHigh
1.4.1 Use of ColorAColour isn’t the only way information is shownView the page in greyscale: errors, links, chartsPartial
1.4.2 Audio ControlAAudio that plays for more than 3 seconds can be paused or mutedLoad the page with sound onPartial
1.4.3 Contrast (Minimum)AA4.5:1 for normal text and 3:1 for large textMeasure text, links and statesHigh
1.4.4 Resize TextAAText at 200% without losing content or functionsZoom the browser to 200%Partial
1.4.5 Images of TextAAReal text instead of images of textCheck banners and buttonsPartial
1.4.10 ReflowAANo horizontal scrolling at 320 CSS pixels wideTest at 320 px, or zoom to 400% at 1280 pxPartial
1.4.11 Non-text ContrastAA3:1 for controls, field borders, icons and essential graphicsMeasure borders, icons and selected statesPartial
1.4.12 Text SpacingAANothing breaks with line height 1.5, paragraph spacing 2 em, letter spacing 0.12 em and word spacing 0.16 emApply those values with CSSPartial
1.4.13 Content on Hover or FocusAAIt can be dismissed, hovered over, and doesn’t disappear on its ownTest tooltips and menus with mouse and keyboardPartial

Principle 2. Operable: 20 criteria

CriterionLevelWhat it requiresHow to test itAuto
2.1.1 KeyboardAEverything works with a keyboardComplete the key tasks without a mousePartial
2.1.2 No Keyboard TrapAYou can always move away with the keyboardTab and Shift+Tab through modals, widgets and iframesPartial
2.1.4 Character Key ShortcutsASingle-key shortcuts can be turned off, remapped or only work on focusTry shortcuts while typing or dictatingLow
2.2.1 Timing AdjustableATime limits can be turned off, extended or adjustedLet sessions and bookings time outLow
2.2.2 Pause, Stop, HideAAutomatic movement lasting more than 5 seconds can be pausedCheck carousels and tickersPartial
2.3.1 Three Flashes or Below ThresholdANothing flashes more than three times a second above the thresholdCheck videos and animationsPartial
2.4.1 Bypass BlocksAA way to skip to the main contentFirst Tab: is there a skip link, or landmarks?Partial
2.4.2 Page TitledAEvery page has a descriptive titleCheck the browser tabsHigh
2.4.3 Focus OrderAFocus follows a logical orderTab through and compare with the visual orderPartial
2.4.4 Link Purpose (In Context)AThe link text or its context explains where it goesLook for “here”, “more”, “read”Partial
2.4.5 Multiple WaysAAMore than one way to reach each pageMenu, search, sitemapLow
2.4.6 Headings and LabelsAAThey describe the topic or purposeRead only the headings and labelsLow
2.4.7 Focus VisibleAAYou can always see which element has focusTab through the pagePartial
2.4.11 Focus Not Obscured (Minimum), newAAThe focused element isn’t completely hiddenSticky headers, cookie banners, chat widgetsPartial
2.5.1 Pointer GesturesAA single-pointer alternative to multipoint or path-based gesturesMaps, zoom, slidersLow
2.5.2 Pointer CancellationAThe action fires on release, or can be undonePress, then drag away before releasingLow
2.5.3 Label in NameAThe accessible name contains the visible textCompare visible text with the accessible namePartial
2.5.4 Motion ActuationAAn alternative to shaking or tilting, and a way to turn it offLook for features that respond to motionLow
2.5.7 Dragging Movements, newAAAn alternative that doesn’t need draggingKanban boards, sliders, sorting, file uploadsLow
2.5.8 Target Size (Minimum), newAAAt least 24×24 CSS pixels or enough spacing, with exceptionsIcons, chips, carousel dotsPartial

Test your site with these criteria in front of you. Sprout’s free scan shows the automated failures on any page in seconds. No sign-up. Scan my website

Principle 3. Understandable: 13 criteria

CriterionLevelWhat it requiresHow to test itAuto
3.1.1 Language of PageACorrect lang attributeCheck the lang on the html elementHigh
3.1.2 Language of PartsAAlang on passages in another languageQuotes or buttons in another languagePartial
3.2.1 On FocusAFocus doesn’t trigger a change of contextTab through the pageLow
3.2.2 On InputAChanging a value doesn’t cause unexpected changesSelects, filters, radio buttonsLow
3.2.3 Consistent NavigationAARepeated navigation keeps the same orderCompare templatesLow
3.2.4 Consistent IdentificationAASame function, same name and iconCompare buttons across pagesLow
3.2.6 Consistent Help, newARepeated help appears in the same relative orderContact details, chat and FAQ on each templateLow
3.3.1 Error IdentificationAThe error is identified and described in textSubmit forms with errorsPartial
3.3.2 Labels or InstructionsAEvery field has a label or instructionsReview the formsPartial
3.3.3 Error SuggestionAAThe message says how to fix the errorTrigger common errorsLow
3.3.4 Error Prevention (Legal, Financial, Data)AAReview, correct, confirm or reverse for legal, financial or data transactionsCheckout, account deletionLow
3.3.7 Redundant Entry, newADon’t ask again for information already given in the same processCheckout and multi-step formsLow
3.3.8 Accessible Authentication (Minimum), newAANo cognitive tests without an alternative; pasting and password managers workLog-in and 2FALow

Principle 4. Robust: 2 criteria

CriterionLevelWhat it requiresHow to test itAuto
4.1.2 Name, Role, ValueAComponents expose their name, role, state and valueThe browser’s accessibility treePartial
4.1.3 Status MessagesAAMessages are announced without moving focusAdd to basket, filter, submit a formLow

4.1.1 Parsing isn’t listed because WCAG 2.2 removed it. If a contract requires reporting against WCAG 2.1, you may still need to include it.

The 55 criteria aren’t enough: conformance requirements

WCAG 2.2 adds five requirements on top of the criteria:

  1. Level: every applicable A and AA criterion.
  2. Full pages: you can’t exclude the part that fails.
  3. Complete processes: if a page is part of a process, the whole process must conform.
  4. Accessibility-supported technologies only.
  5. Non-interference: anything that isn’t accessible can’t block the rest of the page.

That’s why “the home page passes the scan” doesn’t work for an online shop. If the checkout fails at payment, the whole process fails.

What an automated scan catches, and what it misses

A scan is good at repeatable technical failures: missing attributes, a missing language or title, most contrast problems, empty accessible names. It’s poor at anything that needs context: whether alt text describes the image well, whether the focus order makes sense, or whether an error message helps.

So a scan doesn’t prove conformance, and neither does a Lighthouse score of 100. It covers a lot of ground quickly and leaves people’s time for the criteria rated “Low”.

How to prioritise

  1. Blockers: any barrier that stops someone buying, signing up, getting in touch or logging in.
  2. Shared components: menus, modals and form fields. One fix corrects hundreds of pages.
  3. Templates and CMS: if the CMS lets editors publish images without alt text, the failure will come back.
  4. Ongoing checks: a site that conforms today can stop conforming in the next release. Sprout Observability reruns the automated checks every month and shows what got worse.

FAQ

Do I need to meet the AAA criteria? Not to claim AA. The W3C also doesn’t recommend requiring AAA for entire sites, because some content can’t meet it.

Can this checklist be used as an official audit? No. It’s a working guide. A conformance evaluation needs a methodology, a sample of pages and processes, and evidence for each test.

Does meeting WCAG 2.2 AA mean I comply with the EAA? Not automatically. WCAG is a technical standard; the EAA and national laws define who’s covered and what’s required. Meeting WCAG 2.2 AA helps you comply, but the legal answer depends on your service.

Start with what a machine can find. Scan your site for free with Sprout and use this checklist for the rest. No sign-up. Scan my website

The scan is an automated check. It isn’t an audit or a conformance statement.

Sources


Profile of the author

Posted by

Jonathan Bell

Co-founder, Sprout ·

View all posts