What Is WCAG 2.1 Level AA?
WCAG 2.1 became a W3C Recommendation in June 2018. It extended WCAG 2.0 with 17 new success criteria for mobile devices, people with low vision and people with cognitive and learning disabilities, and it kept everything from 2.0.
At Level AA, WCAG 2.1 has 50 success criteria. That is the benchmark in the US Department of Justice rule for state and local government websites, in the European standard EN 301 549, and in most ADA website settlements. If you have been told your site must be "WCAG compliant" without further detail, WCAG 2.1 AA is usually what is meant.
The additions that surprise teams most are Reflow (1.4.10), which requires content to work at 400 percent zoom without scrolling sideways, Non-text Contrast (1.4.11) for icons, input borders and focus indicators, and Text Spacing (1.4.12), which requires layouts to survive larger letter and line spacing.
| Published | June 5, 2018 (W3C Recommendation) |
|---|---|
| Success criteria at Level A and AA | 50 |
| New in 2.1 at Level A and AA | 12 (plus 5 at Level AAA) |
| Referenced by | DOJ ADA Title II rule, EN 301 549, most ADA settlements |
| Newer version | WCAG 2.2 (includes all of 2.1 except 4.1.1) |
Who Needs WCAG 2.1 AA?
- US state and local governments, public universities and transit agencies, under the Department of Justice ADA Title II rule adopted in 2024.
- Businesses serving the public in the US, where WCAG 2.1 AA is the standard most ADA Title III settlements and court orders use.
- Public sector bodies across the EU, and many private companies covered by the European Accessibility Act, through EN 301 549.
- Vendors answering procurement questionnaires that ask for WCAG 2.1 AA conformance.
What WCAG 2.1 Added at Level A and AA
These requirements are not in WCAG 2.0, so older audits and templates often miss them.
1.3.4 Orientation, AA
Pages must work in both portrait and landscape unless a specific orientation is essential.
1.3.5 Identify Input Purpose, AA
Personal data fields such as name, email and address need the right autocomplete values. This checker tests it.
1.4.10 Reflow, AA
Content must reflow into a single column at 320 CSS pixels wide, equivalent to 400 percent zoom, without horizontal scrolling.
1.4.11 Non-text Contrast, AA
Icons, input borders, focus indicators and chart elements need 3:1 contrast against their background.
1.4.12 Text Spacing, AA
Text must not be cut off when people increase line, paragraph, letter or word spacing. This checker tests inline styles that block it.
2.5.1 to 2.5.4 Pointer and Motion, A
Multi-finger gestures need single-pointer alternatives, actions should fire on release, visible labels must match accessible names, and shake-to-act features need alternatives.
What This WCAG 2.1 AA Checker Tests
WCAG 2.1 Level AA has 50 success criteria. This checker runs 62 automated rules, which test 19 of them. The rest need a person to judge, and they are listed here so nothing is missed. Open a principle to see every criterion.
Perceivable 9 of 20 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 1.1.1 Non-text Content | A | Automated (7 rules) |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Manual review |
| 1.2.2 Captions (Prerecorded) | A | Automated (1 rule) |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Manual review |
| 1.2.4 Captions (Live) | AA | Manual review |
| 1.2.5 Audio Description (Prerecorded) | AA | Manual review |
| 1.3.1 Info and Relationships | A | Automated (9 rules) |
| 1.3.2 Meaningful Sequence | A | Manual review |
| 1.3.3 Sensory Characteristics | A | Manual review |
| 1.3.4 Orientationnew in 2.1 | AA | Manual review |
| 1.3.5 Identify Input Purposenew in 2.1 | AA | Automated (1 rule) |
| 1.4.1 Use of Color | A | Automated (1 rule) |
| 1.4.2 Audio Control | A | Automated (1 rule) |
| 1.4.3 Contrast (Minimum) | AA | Automated (1 rule) |
| 1.4.4 Resize Text | AA | Automated (1 rule) |
| 1.4.5 Images of Text | AA | Manual review |
| 1.4.10 Reflownew in 2.1 | AA | Manual review |
| 1.4.11 Non-text Contrastnew in 2.1 | AA | Manual review |
| 1.4.12 Text Spacingnew in 2.1 | AA | Automated (1 rule) |
| 1.4.13 Content on Hover or Focusnew in 2.1 | AA | Manual review |
Operable 6 of 17 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 2.1.1 Keyboard | A | Automated (3 rules) |
| 2.1.2 No Keyboard Trap | A | Manual review |
| 2.1.4 Character Key Shortcutsnew in 2.1 | A | Manual review |
| 2.2.1 Timing Adjustable | A | Automated (1 rule) |
| 2.2.2 Pause, Stop, Hide | A | Automated (2 rules) |
| 2.3.1 Three Flashes or Below Threshold | A | Manual review |
| 2.4.1 Bypass Blocks | A | Automated (1 rule) |
| 2.4.2 Page Titled | A | Automated (1 rule) |
| 2.4.3 Focus Order | A | Manual review |
| 2.4.4 Link Purpose (In Context) | A | Automated (2 rules) |
| 2.4.5 Multiple Ways | AA | Manual review |
| 2.4.6 Headings and Labels | AA | Manual review |
| 2.4.7 Focus Visible | AA | Manual review |
| 2.5.1 Pointer Gesturesnew in 2.1 | A | Manual review |
| 2.5.2 Pointer Cancellationnew in 2.1 | A | Manual review |
| 2.5.3 Label in Namenew in 2.1 | A | Manual review |
| 2.5.4 Motion Actuationnew in 2.1 | A | Manual review |
Understandable 3 of 10 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 3.1.1 Language of Page | A | Automated (3 rules) |
| 3.1.2 Language of Parts | AA | Automated (1 rule) |
| 3.2.1 On Focus | A | Manual review |
| 3.2.2 On Input | A | Manual review |
| 3.2.3 Consistent Navigation | AA | Manual review |
| 3.2.4 Consistent Identification | AA | Manual review |
| 3.3.1 Error Identification | A | Manual review |
| 3.3.2 Labels or Instructions | A | Automated (1 rule) |
| 3.3.3 Error Suggestion | AA | Manual review |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Manual review |
Robust 1 of 3 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 4.1.1 Parsing (obsolete in WCAG 2.2) | A | Manual review |
| 4.1.2 Name, Role, Value | A | Automated (28 rules) |
| 4.1.3 Status Messagesnew in 2.1 | AA | Manual review |
What to Check by Hand
Automated rules find the code-level failures. Add these checks to cover what they cannot judge.
- Zoom the browser to 400 percent, or narrow the window to 320 pixels, and check that nothing needs sideways scrolling (1.4.10).
- Rotate a phone or tablet and confirm the page works in both orientations (1.3.4).
- Check the contrast of icons, input borders and focus outlines against their backgrounds (1.4.11).
- Make sure the visible text of each button matches or starts its accessible name (2.5.3).
- Tab through the page and confirm focus order and visible focus.
- Review alternative text and form error messages for meaning, not just presence.
For a step-by-step routine, see Plan manual testing in our Help Center.
How to Use Your Results
- Fix critical and serious issues first, especially on forms, navigation and checkout. Each issue shows the failing code and how to fix it.
- Filter by criterion to hand one type of issue to the right person, for example contrast to design and labels to development.
- Rescan after each fix to confirm it, then run the manual checks above.
- Monitor the whole site. A free scan checks one page. AccessBell Pro monitors up to 500 URLs per domain against WCAG 2.1 Level AA every day and alerts you to new issues.
Related Guides
WCAG 2.1 AA Checker Questions
Is WCAG 2.1 AA the legal standard for websites?
It is the most common one. The US Department of Justice adopted WCAG 2.1 AA for state and local government websites in 2024, the European standard EN 301 549 uses it for web content, and most ADA website settlements require it. Some laws still reference WCAG 2.0, and WCAG 2.2 is the newest version.
Should I test against WCAG 2.1 or 2.2?
If a contract or law names WCAG 2.1 AA, test against it and report against it. If you are free to choose, test against 2.2 AA: it includes almost everything in 2.1 plus six more A and AA criteria, so you cover both at once.
How many WCAG 2.1 AA criteria can be tested automatically?
Automated rules exist for part of the standard. The coverage table on this page shows exactly which WCAG 2.1 AA criteria this checker tests and which need manual review.
What does a WCAG 2.1 AA report include?
Each failure shows the element that failed, the success criterion and level, its severity and how to fix it. Items the tool cannot decide are listed separately for manual review.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab)
- W3C WAI: What is new in WCAG 2.1 (opens in a new tab)
- ADA.gov: Fact sheet on the ADA Title II web and mobile rule (opens in a new tab)
This page explains technical standards and is not legal advice. See our disclaimer.