WCAG 2.2 quick reference: every A and AA criterion on one page
Updated October 14, 2026 · 3 min read
WCAG 2.2 has 86 success criteria in four principles and 13 guidelines. For a website the relevant part is level AA, which means all 31 level A and 24 level AA criteria — 55 in total. This page lists those 55 in one table, with a plain-language summary and a link to our explanation of each, and gives you a PDF checklist to work through.
This is general information, not legal advice.
WCAG 2.2 in numbers
| What | Count | Notes |
|---|---|---|
| Principles | 4 | Perceivable, Operable, Understandable, Robust |
| Guidelines | 13 | 4 + 5 + 3 + 1 under the four principles |
| Level A criteria | 31 | The minimum |
| Level AA criteria | 24 | A + AA = 55, the level laws refer to |
| Level AAA criteria | 31 | A + AA + AAA = 86 |
| New compared with WCAG 2.1 | 9 | 4.1.1 Parsing is obsolete and removed |
The counts follow the WCAG 2.2 Recommendation. 4.1.1 Parsing still appears in the numbering, marked obsolete and removed, which is why you can count 87 entries but only 86 criteria. More about the levels in WCAG levels A, AA and AAA, and about the new criteria in WCAG 2.1 vs 2.2.
All A and AA criteria
The table shows every level A and AA criterion of WCAG 2.2. Each name links to our explanation; the last column shows whether our automated checks test part of it. Criteria without automated coverage need a manual review.
| Success criterion | Level | What it asks for | Automated check |
|---|---|---|---|
| 1.1.1 Non-text Content | A | WCAG 1.1.1 asks for a text alternative for every image, icon and image button (level A). How to write alt text, when it may be empty, the exceptions and tests. | Partly |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | WCAG 1.2.1 asks for a transcript for recorded audio and a text or audio alternative for silent video (level A). What counts, the exception and how to check it. | Manual review |
| 1.2.2 Captions (Prerecorded) | A | WCAG 1.2.2 asks for captions on all prerecorded video with sound (level A). What captions must include, why auto-captions are not enough and how to check them. | Partly |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | WCAG 1.2.3 asks for audio description or a full text alternative for recorded video (level A). What each option means, when none is needed and how to check it. | Manual review |
| 1.2.4 Captions (Live) | AA | WCAG 1.2.4 asks for captions on live video with sound, such as webinars and live shopping (level AA). What counts as live, what is out of scope, how to check. | Manual review |
| 1.2.5 Audio Description (Prerecorded) | AA | WCAG 1.2.5 asks for audio description of all prerecorded video with sound (level AA). When it is not needed, extended description and how to check your videos. | Manual review |
| 1.3.1 Info and Relationships | A | WCAG 1.3.1 asks that headings, lists, tables and form labels are marked up in code, not only styled (level A). Typical failures, how to test 1.3.1 and fix it. | Partly |
| 1.3.2 Meaningful Sequence | A | WCAG 1.3.2 asks that the order of content in the code keeps its meaning when read aloud (level A). Common CSS layout failures, how to test the order and fix it. | Manual review |
| 1.3.3 Sensory Characteristics | A | WCAG 1.3.3: instructions must not rely only on shape, colour, size, position or sound, like "click the round button" (level A). Examples, how to check and fix. | Manual review |
| 1.3.4 Orientation | AA | WCAG 1.3.4 says a site must not lock its view to portrait or landscape unless one orientation is essential (level AA). What it means, how to test and fix it. | Partly |
| 1.3.5 Identify Input Purpose | AA | WCAG 1.3.5 asks that fields for the user's own data, such as name or email, declare their purpose with autocomplete (level AA). Which fields and how to test. | Partly |
| 1.4.1 Use of Color | A | WCAG 1.4.1: colour must not be the only visual way to show information, like links, errors or stock status (level A). Link rules, examples, testing and fixes. | Partly |
| 1.4.2 Audio Control | A | WCAG 1.4.2 says audio that plays automatically for more than 3 seconds needs a way to pause, stop or control its volume (level A). Failures, testing and fixes. | Partly |
| 1.4.3 Contrast (Minimum) | AA | WCAG 1.4.3 asks for a contrast ratio of at least 4.5:1 for text and 3:1 for large text (level AA). What counts as large text, the exceptions and how to test it. | Partly |
| 1.4.4 Resize Text | AA | WCAG 1.4.4 asks that text can be zoomed to 200% without losing content or functions (level AA). Why blocking zoom fails, the exceptions and how to test it. | Partly |
| 1.4.5 Images of Text | AA | WCAG 1.4.5 asks for real text instead of pictures of text where possible (level AA). Exceptions for logos and essential text, examples, how to check and fix. | Manual review |
| 1.4.10 Reflow | AA | WCAG 1.4.10 asks that pages work at 320 CSS px width, or 400% zoom, without horizontal scrolling (level AA). The exceptions, how to test reflow and fix it. | Manual review |
| 1.4.11 Non-text Contrast | AA | WCAG 1.4.11 asks for 3:1 contrast for icons, form field borders, focus indicators and chart parts (level AA). The exceptions, how to check and fix it. | Manual review |
| 1.4.12 Text Spacing | AA | WCAG 1.4.12: text must still work when users set 1.5 line height, 2× paragraph, 0.12 letter and 0.16 word spacing (level AA). How to test it and fix clipping. | Partly |
| 1.4.13 Content on Hover or Focus | AA | WCAG 1.4.13 asks that tooltips, mega menus and popups shown on hover or focus are dismissible, hoverable and persistent (level AA). What it means, how to test. | Manual review |
| 2.1.1 Keyboard | A | WCAG 2.1.1 asks that every function of a page works with a keyboard alone (level A). What it covers, the one exception and how to test keyboard navigation. | Partly |
| 2.1.2 No Keyboard Trap | A | WCAG 2.1.2 says keyboard focus that enters a component must be able to leave it by keyboard alone (level A). Typical keyboard traps and how to test them. | Manual review |
| 2.1.4 Character Key Shortcuts | A | WCAG 2.1.4: single-character keyboard shortcuts must be possible to turn off, remap or limit to a focused control (level A). Examples and how to test. | Manual review |
| 2.2.1 Timing Adjustable | A | WCAG 2.2.1 asks that users can turn off, adjust or extend time limits, with a warning and 20 seconds to extend (level A). Exceptions, timeouts and tests. | Partly |
| 2.2.2 Pause, Stop, Hide | A | WCAG 2.2.2 asks for a way to pause, stop or hide content that moves for over five seconds or auto-updates (level A). Carousels, tickers and testing. | Partly |
| 2.3.1 Three Flashes or Below Threshold | A | WCAG 2.3.1 forbids content that flashes more than three times in any one second unless it is below the flash thresholds (level A). What counts, how to test. | Manual review |
| 2.4.1 Bypass Blocks | A | WCAG 2.4.1 asks for a way to skip blocks repeated on every page, such as the menu (level A). Skip links, landmarks, headings, shop failures and testing. | Partly |
| 2.4.2 Page Titled | A | WCAG 2.4.2 asks every web page to have a title that describes its topic or purpose (level A). Good titles for shops and single-page apps, and how to test. | Partly |
| 2.4.3 Focus Order | A | WCAG 2.4.3 asks that keyboard focus moves in an order that keeps meaning and operation intact (level A). Positive tabindex, popups and how to test. | Manual review |
| 2.4.4 Link Purpose (In Context) | A | WCAG 2.4.4 asks that the purpose of each link is clear from its text or context (level A). Why "Read more" and empty icon links fail, and how to fix them. | Partly |
| 2.4.5 Multiple Ways | AA | WCAG 2.4.5 asks for more than one way to find a page, such as menu plus search or a site map (level AA). The checkout exception, examples and testing. | Manual review |
| 2.4.6 Headings and Labels | AA | WCAG 2.4.6 asks that headings and labels describe their topic or purpose (level AA). What it does not require, heading order, form labels and testing. | Manual review |
| 2.4.7 Focus Visible | AA | WCAG 2.4.7 asks that keyboard focus is always visible (level AA). Why outline: none breaks it, how it differs from 2.4.13 and how to test the indicator. | Manual review |
| 2.4.11 Focus Not Obscured (Minimum) (new in 2.2) | AA | WCAG 2.4.11 (new in 2.2, AA): a focused element must not be entirely hidden by sticky headers, cookie banners or other author content. Exceptions, tests. | Manual review |
| 2.5.1 Pointer Gestures | A | WCAG 2.5.1 asks that pinch, swipe and other multipoint or path-based gestures also work with a single tap or click (level A). Examples and testing. | Manual review |
| 2.5.2 Pointer Cancellation | A | WCAG 2.5.2 asks that pointer actions do not fire on press, so accidental taps can be cancelled or undone (level A). The four options and how to test. | Manual review |
| 2.5.3 Label in Name | A | WCAG 2.5.3 asks that the accessible name of a control contains its visible label text (level A), so voice users can say what they see. Failures and fixes. | Partly |
| 2.5.4 Motion Actuation | A | WCAG 2.5.4: features triggered by shaking or tilting a device must also work with on-screen controls, and motion can be turned off (level A). Examples. | Manual review |
| 2.5.7 Dragging Movements (new in 2.2) | AA | WCAG 2.5.7 (new in 2.2, AA) asks that anything done by dragging can also be done with a single pointer without dragging. Sliders, lists, maps, testing. | Manual review |
| 2.5.8 Target Size (Minimum) (new in 2.2) | AA | WCAG 2.5.8 (new in 2.2, AA) asks for click and touch targets of at least 24×24 CSS pixels or enough spacing. The five exceptions, examples and tests. | Partly |
| 3.1.1 Language of Page | A | WCAG 3.1.1 asks that the main language of every page can be read by software, usually via the html lang attribute (level A). What it means and how to check it. | Partly |
| 3.1.2 Language of Parts | AA | WCAG 3.1.2 asks you to mark passages in another language with a lang attribute (level AA). The exceptions for names and terms, typical shop failures and fixes. | Partly |
| 3.2.1 On Focus | A | WCAG 3.2.1 says that moving focus to a control must not change the context, such as opening a window or a new page (level A). Shop examples and how to test it. | Manual review |
| 3.2.2 On Input | A | WCAG 3.2.2 says changing a field, checkbox or select must not change the context unless users were told first (level A). Shop failures, testing and fixes. | Manual review |
| 3.2.3 Consistent Navigation | AA | WCAG 3.2.3 asks that menus and other navigation repeated across pages keep the same relative order (level AA). What it allows, shop failures and how to check. | Manual review |
| 3.2.4 Consistent Identification | AA | WCAG 3.2.4 asks that components with the same function are labelled the same way across a site (level AA). What counts, typical shop failures and how to check. | Manual review |
| 3.2.6 Consistent Help (new in 2.2) | A | WCAG 3.2.6, new in WCAG 2.2, asks that contact details, chat and help links repeated across pages stay in the same order (level A). What it covers, how to test. | Manual review |
| 3.3.1 Error Identification | A | WCAG 3.3.1 asks that form errors are pointed out and described in text, including empty required fields (level A). Shop failures, how to test and how to fix. | Manual review |
| 3.3.2 Labels or Instructions | A | WCAG 3.3.2 asks for labels or instructions wherever a form expects input, optional fields included (level A). Placeholders, required fields and how to check. | Partly |
| 3.3.3 Error Suggestion | AA | WCAG 3.3.3 asks that when a form error is detected and a fix is known, the fix is suggested to the user (level AA). The security exception, examples and tests. | Manual review |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | WCAG 3.3.4 asks that orders, payments and data deletion are reversible, checked or confirmed before they are final (level AA). What it means for a checkout. | Manual review |
| 3.3.7 Redundant Entry (new in 2.2) | A | WCAG 3.3.7, new in WCAG 2.2: data already entered in a process must be filled in or offered for selection, not typed again (level A). Exceptions and tests. | Manual review |
| 3.3.8 Accessible Authentication (Minimum) (new in 2.2) | AA | WCAG 3.3.8, new in 2.2, bans memory and puzzle tests at login unless there is an alternative or help such as paste and password managers (AA). Captcha rules. | Manual review |
| 4.1.2 Name, Role, Value | A | WCAG 4.1.2 asks that every button, link and form control exposes its name, role and state to assistive technology (level A). ARIA failures in shops and fixes. | Partly |
| 4.1.3 Status Messages | AA | WCAG 4.1.3 asks that messages like "Added to cart" or "12 results" are announced by screen readers without moving focus (level AA). role=status, alert, fixes. | Manual review |
The official W3C quick reference
The W3C publishes its own customizable quick reference, How to Meet WCAG (Quick Reference). It lists the success criteria together with the W3C's sufficient and advisory techniques and documented failures, and you can filter it by level, by technology (HTML, CSS, ARIA, scripting, PDF and others) and by WCAG version. It is the reference for developers who want to know how a criterion can be met; our table above is the short version for deciding what to look at first.
How to use this reference
- Start with an automated check. Our free WCAG checker tests one page against the criteria that can be tested automatically and explains each finding in plain words.
- Walk through the rest by hand. Keyboard, focus, zoom and screen reader steps are in how to test WCAG.
- Track it. Use the checklist below, or the web version in the WCAG 2.2 checklist.
Our checks are an automated check, not a full audit, and not legal advice. The background of the guidelines is on our WCAG overview.
Download as a PDF checklist
Download the checklist as a PDF
Every success criterion of levels A and AA with what to check and a tick box. Free, with a link by e-mail.
Frequently asked questions
How many success criteria does WCAG 2.2 have?
86: 31 at level A, 24 at level AA and 31 at level AAA. The numbering goes up to 87 entries because 4.1.1 Parsing is kept as obsolete and removed.
How many WCAG 2.2 AA criteria are there?
24 criteria have level AA. Meeting level AA means meeting those 24 and the 31 level A criteria, so 55 success criteria in total.
How many guidelines does WCAG 2.2 have?
13 guidelines under 4 principles: 4 under Perceivable, 5 under Operable, 3 under Understandable and 1 under Robust. The testable requirements are the success criteria inside the guidelines.
Where is the official W3C quick reference?
The W3C publishes "How to Meet WCAG (Quick Reference)" at w3.org/WAI/WCAG22/quickref. It lists all success criteria with their techniques and failures and can be filtered by level, technology and version.
How many criteria are new in WCAG 2.2?
Nine new success criteria compared with WCAG 2.1; 4.1.1 Parsing was removed. Six of the new ones are at level A or AA.
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2: https://www.w3.org/TR/WCAG22/
- W3C, How to Meet WCAG (Quick Reference): https://www.w3.org/WAI/WCAG22/quickref/
- W3C, What's new in WCAG 2.2: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/