WCAG 2.1 AA checklist: all 50 criteria in plain words
A WCAG 2.1 AA checklist covers 50 success criteria: 30 at Level A and 20 at Level AA. Passing means every one of them is met on the pages you test, or does not apply. Below is the full list in plain words, grouped by what a visitor experiences, with a note on which ones a free scanner can check and which need you to look. Courts and settlements most often point to this standard when they judge a business website, though no US rule names it for private businesses. We are not lawyers; this is not legal advice.
How to use this WCAG 2.1 AA checklist
- Pick your key pages: home, a service or product, the contact or checkout page, and one long page.
- Run a free scanner first (see our Chrome extension guide). Scanners test the rows marked scan below, and only part of those.
- Go through the rows marked look yourself with the keyboard, zoom and your own eyes.
- Write pass, fail or not applicable beside each criterion, with the page and the element.
- Fix in the order at the end, then rescan.
Verify wording against the W3C's own text, the WCAG 2.1 Quick Reference, before you rely on any checklist, including this one; some published lists place criteria at the wrong level (for example 44 by 44 pixel touch targets, which is a Level AAA criterion in 2.1).
1. Perceivable: can people see, hear or read it?
| No. | Level | Plain words | How to test |
|---|---|---|---|
| 1.1.1 Non-text content | A | Every meaningful image has alt text; decoration has empty alt | scan, then look |
| 1.2.1 Audio-only, video-only | A | A transcript or alternative for recorded audio or silent video | look |
| 1.2.2 Captions (recorded) | A | Videos with sound have captions | look |
| 1.2.3 Audio description or alternative | A | Video has a description or a text version | look |
| 1.2.4 Captions (live) | AA | Live video has captions | look |
| 1.2.5 Audio description (recorded) | AA | Recorded video has audio description | look |
| 1.3.1 Info and relationships | A | Headings, lists, tables and form labels are real markup | scan, then look |
| 1.3.2 Meaningful sequence | A | The reading order makes sense without the styling | look |
| 1.3.3 Sensory characteristics | A | Instructions do not rely only on shape, colour or position | look |
| 1.3.4 Orientation | AA | Works in portrait and landscape | look |
| 1.3.5 Identify input purpose | AA | Name, email and address fields say what they are, so browsers can fill them | scan |
| 1.4.1 Use of colour | A | Colour is not the only way to show something (link, error) | look |
| 1.4.2 Audio control | A | Sound that plays over 3 seconds can be paused | look |
| 1.4.3 Contrast (minimum) | AA | Text is at least 4.5 to 1 against its background (3 to 1 for large text) | scan |
| 1.4.4 Resize text | AA | Text zooms to 200 per cent with nothing lost | look |
| 1.4.5 Images of text | AA | Real text instead of text in a picture | look |
| 1.4.10 Reflow | AA | At 400 per cent zoom, no sideways scrolling for main content | look |
| 1.4.11 Non-text contrast | AA | Buttons, fields and icons are at least 3 to 1 against neighbours | look |
| 1.4.12 Text spacing | AA | Nothing breaks if a user increases line, letter and word spacing | look |
| 1.4.13 Content on hover or focus | AA | Pop-ups from hover or focus can be dismissed and do not vanish when you reach them | look |
The two rows scanners do best at are 1.1.1 (finding images with no alt attribute at all) and 1.4.3 (colours). Our colour contrast checker guide shows how to fix a failing colour in a minute.
2. Operable: can people use it without a mouse?
| No. | Level | Plain words | How to test |
|---|---|---|---|
| 2.1.1 Keyboard | A | Everything works with the keyboard alone | look |
| 2.1.2 No keyboard trap | A | You can always tab out of a widget | look |
| 2.1.4 Character key shortcuts | A | Single-key shortcuts can be turned off or changed | look |
| 2.2.1 Timing adjustable | A | Time limits can be extended or removed | look |
| 2.2.2 Pause, stop, hide | A | Moving or auto-updating content (sliders) can be stopped | look |
| 2.3.1 Three flashes | A | Nothing flashes more than three times a second | look |
| 2.4.1 Bypass blocks | A | A skip link or landmarks let people jump past the menu | scan, then look |
| 2.4.2 Page titled | A | Each page has a clear title | scan |
| 2.4.3 Focus order | A | Tab order follows the visual order | look |
| 2.4.4 Link purpose | A | Link text makes sense in context | scan, then look |
| 2.4.5 Multiple ways | AA | More than one way to find a page (menu, search, sitemap) | look |
| 2.4.6 Headings and labels | AA | Headings and labels describe their content | look |
| 2.4.7 Focus visible | AA | You can see where the keyboard focus is | look |
| 2.5.1 Pointer gestures | A | Anything done with a swipe or pinch also works with a tap | look |
| 2.5.2 Pointer cancellation | A | A tap triggers on release, so a slip can be undone | look |
| 2.5.3 Label in name | A | A button's spoken name contains its visible words | scan, then look |
| 2.5.4 Motion actuation | A | Shaking or tilting is never the only way to act | look |
2.1.1 and 2.4.7 are the ones that fail most on small business sites. Press Tab from the top of the page. If the focus outline disappears, a theme has turned it off, which is usually one line of style code to restore.
3. Understandable: is it clear and predictable?
| No. | Level | Plain words | How to test |
|---|---|---|---|
| 3.1.1 Language of page | A | The page declares its language | scan |
| 3.1.2 Language of parts | AA | A passage in another language is marked | scan, then look |
| 3.2.1 On focus | A | Landing on a field does not change the page | look |
| 3.2.2 On input | A | Entering a value does not submit or jump without warning | look |
| 3.2.3 Consistent navigation | AA | Menus stay in the same place and order | look |
| 3.2.4 Consistent identification | AA | Same function, same name everywhere | look |
| 3.3.1 Error identification | A | Form errors are described in text | look |
| 3.3.2 Labels or instructions | A | Every field has a visible label | scan, then look |
| 3.3.3 Error suggestion | AA | The error says how to fix it | look |
| 3.3.4 Error prevention | AA | Payments and legal forms can be reviewed, corrected or undone | look |
4. Robust: does it work with assistive technology?
| No. | Level | Plain words | How to test |
|---|---|---|---|
| 4.1.1 Parsing | A | Valid markup, no duplicate IDs (obsolete in 2.2, still listed in 2.1) | scan |
| 4.1.2 Name, role, value | A | Custom controls tell a screen reader what they are and their state | scan, then look |
| 4.1.3 Status messages | AA | "Added to cart" and similar messages are announced | look |
What the 2.1 AA checklist adds to 2.0
WCAG 2.1 kept every 2.0 criterion and added 17, twelve of them at A or AA: 1.3.4, 1.3.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.4, 2.5.1, 2.5.2, 2.5.3, 2.5.4 and 4.1.3. They mostly concern phones, zoom and low vision. WCAG 2.2 followed in October 2023 with nine more and dropped 4.1.1. In April 2024 the US Department of Justice adopted WCAG 2.1 AA for state and local government websites; private businesses have no such rule, but the standard is the one people will reach for.
What to fix first on a small site
- Contrast (1.4.3) and focus outline (2.4.7). Quick style changes with large effect.
- Alt text (1.1.1) and link names (2.4.4). Content edits you can make today.
- Form labels and errors (3.3.1, 3.3.2, 3.3.3). They block sales and contact messages.
- Keyboard access (2.1.1, 2.1.2). Menus, pop-ups and sliders; often a theme issue.
- Headings and page titles (1.3.1, 2.4.2, 2.4.6).
- Video captions (1.2.2) and zoom (1.4.4, 1.4.10).
The shorter ADA compliant website checklist turns these into 25 checks you can run in a week, and free checkers will do the scanning part. Publish an honest accessibility statement once you have a pass list.
Can a scanner pass a site for WCAG 2.1 AA?
No. Automated tools detect only a part of the criteria, and for those they can say "no errors found", not "accessible". A scan with zero errors can sit on a site where a keyboard user cannot reach the checkout. That is why the table has a "look" column, and why an overlay widget cannot settle it either: the FTC's January 2025 order against accessiBe was about claims that its tool made sites WCAG compliant.
For the legal background, read ADA website compliance requirements.
Frequently asked questions
How many criteria are in WCAG 2.1 AA?
50: 30 at Level A and 20 at Level AA. WCAG 2.1 has 78 in total, with 28 more at Level AAA.
Is WCAG 2.1 AA required by the ADA?
The ADA does not name a standard for private websites. Courts and settlements usually use WCAG 2.1 AA, and government sites have a rule naming it.
What is the difference between WCAG 2.1 and 2.2?
2.2 adds nine criteria, including a minimum target size of 24 pixels, and removes 4.1.1 Parsing.
Is there a WCAG 2.1 AA checklist PDF?
Several vendors publish one. Check any list against the W3C Quick Reference; this page is the same list as a web page you can print.
What do I fix first?
Contrast, focus outline, alt text, form labels and keyboard access.
How long does a WCAG 2.1 AA check take?
A scan takes minutes. A careful manual pass through key pages takes hours; a full audit of a larger site takes longer.
Want a version you can print? Use the WCAG 2.1 AA checklist PDF, a 30-check sheet with pass boxes.
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.1 and the WCAG 2.1 Quick Reference (w3.org/WAI/WCAG21/quickref).
- W3C, WCAG 2.2, October 2023.
- US Department of Justice, final rule on web accessibility for state and local governments, April 2024.
- Level Access, accessiBe and Askem WCAG checklists, read 2026-11-15 for comparison.
- FTC, order against accessiBe, January 2025.