Power Your Software Testing with AI Agents and Cloud
The Native AI-Agentic Cloud Platform to Supercharge Quality Engineering. Test Intelligently and Ship Faster.
- TestMu AI (Formerly LambdaTest)
- /
- Blog
- /
- WCAG 2.1 AA: All 78 Success Criteria + Checklist
WCAG 2.1: Every Success Criterion Explained, With an AA Checklist
WCAG 2.1 AA explained: all 50 Level A and AA success criteria in plain words, the 17 criteria added since WCAG 2.0, and which laws require 2.1 AA, with deadlines.
Published on:
WCAG 2.1 Level AA is the accessibility standard that the US ADA Title II rule requires of state and local governments, so it is the version most compliance audits are measured against right now.
This guide lists all 50 Level A and AA success criteria in plain words, the 17 criteria WCAG 2.1 added to WCAG 2.0, the 28 Level AAA criteria, which laws require 2.1 AA, and how WCAG 2.1 relates to 2.2. Where the TestMu AI scanner checks a criterion, its name links to the rule documentation.
TL;DR
WCAG 2.1 became a W3C Recommendation on 5 June 2018. It has 78 success criteria: 30 at Level A, 20 at Level AA, and 28 at Level AAA. A WCAG 2.1 AA audit covers the 50 Level A and AA criteria.
- Required by the ADA Title II rule: State and local governments must meet WCAG 2.1 AA by April 26, 2027 if they serve 50,000 or more people, and by April 26, 2028 if they are smaller or a special district government.
- 17 criteria added to WCAG 2.0: 12 at Level A or AA, covering mobile use, low vision, and cognitive needs, such as 1.3.4 Orientation, 1.4.10 Reflow, and 4.1.3 Status Messages.
- Superseded, but still the legal baseline: WCAG 2.2 adds 9 criteria and removes 4.1.1 Parsing, and content that conforms to WCAG 2.2 also conforms to WCAG 2.1.
What Is WCAG 2.1?
WCAG 2.1 is version 2.1 of the Web Content Accessibility Guidelines, the W3C standard for making web content accessible to people with disabilities. The W3C first published it as a Recommendation on 5 June 2018, and the current edition of the WCAG 2.1 Recommendation is dated 6 May 2025.
Like every WCAG 2 version, it groups its success criteria under four principles: Perceivable, Operable, Understandable, and Robust. WCAG 2.1 has 13 guidelines, one more than WCAG 2.0, because it adds Guideline 2.5 Input Modalities for pointer, touch, and motion input. For the principles and how the levels work, see the guide to WCAG 2.2, the current version.
Who Must Meet WCAG 2.1 AA?
WCAG is a W3C standard rather than a law, but several rules adopt WCAG 2.1 Level AA as their technical standard:
- US state and local governments - The Department of Justice ADA Title II web rule requires WCAG 2.1 Level AA for their web content and mobile apps, including contractors acting for them.
- Europe - EN 301 549 V3.2.1, the European standard for accessible ICT, references WCAG 2.1 for web content.
- US federal agencies - The Revised Section 508 Standards reference WCAG 2.0 Level A and AA. WCAG 2.1 includes every WCAG 2.0 criterion, so a site that meets 2.1 AA also meets the Section 508 requirement.
- Private businesses - The ADA statute does not name a WCAG version for businesses under ADA Title III, but WCAG 2.1 AA is the level most audits measure against.
ADA Title II Deadlines
An interim final rule published in the Federal Register on April 20, 2026 extended the Title II compliance dates by one year:
- Population 50,000 or more - WCAG 2.1 Level AA by April 26, 2027.
- Under 50,000 and special district governments - WCAG 2.1 Level AA by April 26, 2028.
The ADA Title II checklist covers the exceptions in the rule and a step-by-step plan for meeting it.
What Changed From WCAG 2.0 to 2.1?
According to the W3C summary of what is new in WCAG 2.1, WCAG 2.1 adds 17 success criteria and changes none of the WCAG 2.0 criteria. Twelve of them apply at Level A or AA, so they are part of a WCAG 2.1 AA audit.
| Success Criterion | Level | What It Requires |
|---|---|---|
| 1.3.4 Orientation | AA | Content works in both portrait and landscape unless one orientation is essential. |
| 1.3.5 Identify Input Purpose | AA | Fields that collect personal data, such as name, email, and address, declare their purpose, for example with the HTML autocomplete attribute. |
| 1.4.10 Reflow | AA | Content fits a 320 CSS pixel wide viewport, the same as 400% zoom, without scrolling in two directions. |
| 1.4.11 Non-text Contrast | AA | Buttons, form field borders, focus indicators, and meaningful graphics have at least 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | AA | Nothing is cut off or overlaps when users increase line height, paragraph, letter, and word spacing. |
| 1.4.13 Content on Hover or Focus | AA | Tooltips and pop-ups that appear on hover or focus can be dismissed, can be hovered over, and stay visible until dismissed. |
| 2.1.4 Character Key Shortcuts | A | Single-key shortcuts can be turned off, remapped, or work only when the component has focus. |
| 2.5.1 Pointer Gestures | A | Multipoint or path-based gestures, such as pinch or swipe, have a single-pointer alternative such as a tap. |
| 2.5.2 Pointer Cancellation | A | Actions run when the pointer is released, not when it is pressed, or can be aborted or undone. |
| 2.5.3 Label in Name | A | The accessible name of a control includes its visible label text, so voice users can say what they see. |
| 2.5.4 Motion Actuation | A | Features triggered by shaking or tilting the device can also be operated with a control and can be turned off. |
| 4.1.3 Status Messages | AA | Status messages, such as "item added to cart", are announced by screen readers without moving focus. |
| 1.3.6 Identify Purpose | AAA | The purpose of components, icons, and regions can be identified by software. |
| 2.2.6 Timeouts | AAA | Users are told how long inactivity can last before data is lost. |
| 2.3.3 Animation from Interactions | AAA | Motion triggered by user interaction can be turned off. |
| 2.5.5 Target Size | AAA | Pointer targets are at least 44 by 44 CSS pixels. |
| 2.5.6 Concurrent Input Mechanisms | AAA | Users can switch between input methods, such as touch, mouse, and keyboard. |
WCAG 2.1 AA Checklist: All 50 Success Criteria
A page conforms to WCAG 2.1 Level AA when it meets all 30 Level A and all 20 Level AA success criteria below. The Added In column shows which criteria are new since WCAG 2.0.
| Success Criterion | Level | Added In | What It Requires |
|---|---|---|---|
| 1.1.1 Non-text Content | A | WCAG 2.0 | Images, icons, and other non-text content have a text alternative that serves the same purpose; decorative images are hidden from assistive technology. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | WCAG 2.0 | Prerecorded audio has a transcript, and prerecorded silent video has a text or audio alternative. |
| 1.2.2 Captions (Prerecorded) | A | WCAG 2.0 | Prerecorded video with audio has synchronized captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | WCAG 2.0 | Prerecorded video has audio description or a full text alternative. |
| 1.2.4 Captions (Live) | AA | WCAG 2.0 | Live video with audio has real-time captions. |
| 1.2.5 Audio Description (Prerecorded) | AA | WCAG 2.0 | Prerecorded video has audio description of important visual information. |
| 1.3.1 Info and Relationships | A | WCAG 2.0 | Headings, lists, tables, and form labels are marked up so their structure reaches assistive technology. |
| 1.3.2 Meaningful Sequence | A | WCAG 2.0 | The reading order in the code matches the meaningful order of the content. |
| 1.3.3 Sensory Characteristics | A | WCAG 2.0 | Instructions do not rely only on shape, size, position, or sound, such as "press the round button on the right". |
| 1.3.4 Orientation | AA | WCAG 2.1 | Content works in both portrait and landscape unless one orientation is essential. |
| 1.3.5 Identify Input Purpose | AA | WCAG 2.1 | Fields that collect personal data, such as name, email, and address, declare their purpose, for example with the HTML autocomplete attribute. |
| 1.4.1 Use of Color | A | WCAG 2.0 | Color is not the only way information is shown, such as a red border alone marking an error. |
| 1.4.2 Audio Control | A | WCAG 2.0 | Audio that plays automatically for more than 3 seconds can be paused, stopped, or turned down. |
| 1.4.3 Contrast (Minimum) | AA | WCAG 2.0 | Text has a contrast ratio of at least 4.5:1, or 3:1 for large text. |
| 1.4.4 Resize Text | AA | WCAG 2.0 | Text can be resized to 200% without loss of content or function. |
| 1.4.5 Images of Text | AA | WCAG 2.0 | Real text is used instead of images of text, except for logos and where the presentation is essential. |
| 1.4.10 Reflow | AA | WCAG 2.1 | Content fits a 320 CSS pixel wide viewport, the same as 400% zoom, without scrolling in two directions. |
| 1.4.11 Non-text Contrast | AA | WCAG 2.1 | Buttons, form field borders, focus indicators, and meaningful graphics have at least 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | AA | WCAG 2.1 | Nothing is cut off or overlaps when users increase line height, paragraph, letter, and word spacing. |
| 1.4.13 Content on Hover or Focus | AA | WCAG 2.1 | Tooltips and pop-ups that appear on hover or focus can be dismissed, can be hovered over, and stay visible until dismissed. |
| 2.1.1 Keyboard | A | WCAG 2.0 | Every function works with a keyboard alone. |
| 2.1.2 No Keyboard Trap | A | WCAG 2.0 | Keyboard focus can always move away from any component. |
| 2.1.4 Character Key Shortcuts | A | WCAG 2.1 | Single-key shortcuts can be turned off, remapped, or work only when the component has focus. |
| 2.2.1 Timing Adjustable | A | WCAG 2.0 | Users can turn off, adjust, or extend time limits. |
| 2.2.2 Pause, Stop, Hide | A | WCAG 2.0 | Moving, blinking, scrolling, or auto-updating content can be paused, stopped, or hidden. |
| 2.3.1 Three Flashes or Below Threshold | A | WCAG 2.0 | Nothing flashes more than three times in any one second, or the flashes stay below the general and red flash thresholds. |
| 2.4.1 Bypass Blocks | A | WCAG 2.0 | Users can skip repeated blocks such as the navigation, for example with a skip link or landmarks. |
| 2.4.2 Page Titled | A | WCAG 2.0 | Each page has a title that describes its topic or purpose. |
| 2.4.3 Focus Order | A | WCAG 2.0 | Focus moves through the page in an order that preserves meaning and operation. |
| 2.4.4 Link Purpose (In Context) | A | WCAG 2.0 | The purpose of each link is clear from its text or its surrounding context. |
| 2.4.5 Multiple Ways | AA | WCAG 2.0 | There is more than one way to find a page, such as navigation, search, or a site map. |
| 2.4.6 Headings and Labels | AA | WCAG 2.0 | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | AA | WCAG 2.0 | The keyboard focus indicator is visible. |
| 2.5.1 Pointer Gestures | A | WCAG 2.1 | Multipoint or path-based gestures, such as pinch or swipe, have a single-pointer alternative such as a tap. |
| 2.5.2 Pointer Cancellation | A | WCAG 2.1 | Actions run when the pointer is released, not when it is pressed, or can be aborted or undone. |
| 2.5.3 Label in Name | A | WCAG 2.1 | The accessible name of a control includes its visible label text, so voice users can say what they see. |
| 2.5.4 Motion Actuation | A | WCAG 2.1 | Features triggered by shaking or tilting the device can also be operated with a control and can be turned off. |
| 3.1.1 Language of Page | A | WCAG 2.0 | The page declares its default language. |
| 3.1.2 Language of Parts | AA | WCAG 2.0 | Passages in another language are marked with their language. |
| 3.2.1 On Focus | A | WCAG 2.0 | Moving focus to a component does not trigger a change of context. |
| 3.2.2 On Input | A | WCAG 2.0 | Changing a setting does not change the context unless users are told beforehand. |
| 3.2.3 Consistent Navigation | AA | WCAG 2.0 | Navigation repeated across pages appears in the same order. |
| 3.2.4 Consistent Identification | AA | WCAG 2.0 | Components with the same function are identified the same way across pages. |
| 3.3.1 Error Identification | A | WCAG 2.0 | Input errors are identified and described to the user in text. |
| 3.3.2 Labels or Instructions | A | WCAG 2.0 | Fields have labels or instructions when user input is required. |
| 3.3.3 Error Suggestion | AA | WCAG 2.0 | When an input error is detected and a fix is known, the suggestion is shown to the user. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | WCAG 2.0 | Submissions with legal or financial effect, or that change stored data, can be reversed, checked, or confirmed. |
| 4.1.1 Parsing | A | WCAG 2.0 | Markup has no errors that break assistive technology. The W3C now says to treat it as always satisfied for HTML and XML content. |
| 4.1.2 Name, Role, Value | A | WCAG 2.0 | Every component exposes its name, role, state, and value to assistive technology. |
| 4.1.3 Status Messages | AA | WCAG 2.1 | Status messages, such as "item added to cart", are announced by screen readers without moving focus. |
WCAG 2.1 Level AAA Success Criteria
Level AAA has 28 more criteria. No law cited above requires them, and the W3C does not recommend AAA as a general policy for entire sites, because some content cannot meet every AAA criterion. Many teams adopt individual AAA criteria where they help their users.
| Success Criterion | Added In | What It Requires |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) | WCAG 2.0 | Prerecorded audio in video has sign language interpretation. |
| 1.2.7 Extended Audio Description (Prerecorded) | WCAG 2.0 | Video pauses to fit audio description where natural pauses are too short. |
| 1.2.8 Media Alternative (Prerecorded) | WCAG 2.0 | Prerecorded media has a full text alternative. |
| 1.2.9 Audio-only (Live) | WCAG 2.0 | Live audio-only content has a text alternative, such as live captions. |
| 1.3.6 Identify Purpose | WCAG 2.1 | The purpose of components, icons, and regions can be identified by software. |
| 1.4.6 Contrast (Enhanced) | WCAG 2.0 | Text has a contrast ratio of at least 7:1, or 4.5:1 for large text. |
| 1.4.7 Low or No Background Audio | WCAG 2.0 | Recorded speech has no background sound, or background sound that is much quieter. |
| 1.4.8 Visual Presentation | WCAG 2.0 | Users can choose colors, lines are limited in width, text is not justified, and spacing is generous. |
| 1.4.9 Images of Text (No Exception) | WCAG 2.0 | Images of text are used only for decoration or where the presentation is essential. |
| 2.1.3 Keyboard (No Exception) | WCAG 2.0 | Every function works by keyboard, with no exceptions. |
| 2.2.3 No Timing | WCAG 2.0 | Timing is not an essential part of any activity. |
| 2.2.4 Interruptions | WCAG 2.0 | Users can postpone or suppress interruptions. |
| 2.2.5 Re-authenticating | WCAG 2.0 | Data is kept when a session expires and the user signs in again. |
| 2.2.6 Timeouts | WCAG 2.1 | Users are told how long inactivity can last before data is lost. |
| 2.3.2 Three Flashes | WCAG 2.0 | Nothing flashes more than three times in any one second. |
| 2.3.3 Animation from Interactions | WCAG 2.1 | Motion triggered by user interaction can be turned off. |
| 2.4.8 Location | WCAG 2.0 | Users can tell where they are within a set of pages. |
| 2.4.9 Link Purpose (Link Only) | WCAG 2.0 | The purpose of each link is clear from the link text alone. |
| 2.4.10 Section Headings | WCAG 2.0 | Sections of content are organized with headings. |
| 2.5.5 Target Size | WCAG 2.1 | Pointer targets are at least 44 by 44 CSS pixels. |
| 2.5.6 Concurrent Input Mechanisms | WCAG 2.1 | Users can switch between input methods, such as touch, mouse, and keyboard. |
| 3.1.3 Unusual Words | WCAG 2.0 | Definitions are available for jargon, idioms, and unusual words. |
| 3.1.4 Abbreviations | WCAG 2.0 | The expanded form of abbreviations is available. |
| 3.1.5 Reading Level | WCAG 2.0 | A simpler version is available when text needs more than a lower secondary reading level. |
| 3.1.6 Pronunciation | WCAG 2.0 | Pronunciation is available where meaning depends on it. |
| 3.2.5 Change on Request | WCAG 2.0 | Changes of context happen only when the user asks for them. |
| 3.3.5 Help | WCAG 2.0 | Context-sensitive help is available. |
| 3.3.6 Error Prevention (All) | WCAG 2.0 | All submissions can be reversed, checked, or confirmed. |
WCAG 2.1 vs WCAG 2.2
The WCAG 2.2 Recommendation, published on 5 October 2023, keeps every WCAG 2.1 criterion except 4.1.1 Parsing and adds 9 new ones, six of them at Level A or AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, and 3.3.8 Accessible Authentication (Minimum).
The W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.1. If a law or contract names WCAG 2.1 AA, report against 2.1 AA, and treat those six criteria as the next step so the site is ready when rules move to 2.2.
How to Test for WCAG 2.1 AA
Automated scans find failures that can be read from the code, such as missing alt text, low contrast, and missing form labels. Criteria that need judgment, such as focus order, meaningful link text, and captions that match the audio, need a manual pass with a keyboard and a screen reader. The full process is in the guide to accessibility testing.
- Scan every page template - Run an automated WCAG 2.1 AA scan on each template and on key flows such as sign-up, search, and checkout.
- Check the new 2.1 criteria by hand - Rotate a phone for 1.3.4, zoom to 400% for 1.4.10, apply larger text spacing for 1.4.12, and try every swipe or drag with a single tap for 2.5.1.
- Test with a keyboard and a screen reader - Confirm focus order, visible focus, and that status messages are announced without moving focus.
- Record each failure against its criterion - Note the success criterion, the page, and the fix, and retest after each release.
If you run automated accessibility testing on TestMu AI, set the accessibility.wcagVersion capability to wcag21aa so results map to WCAG 2.1 AA. For a quick check of one live page, use the website accessibility checker.
Conclusion
WCAG 2.1 AA is 50 success criteria, and the ADA Title II rule makes it the target for US public entities by 2027 or 2028. Start with the 12 Level A and AA criteria that WCAG 2.1 added to 2.0, since older audits often miss them, then work through the full checklist and keep testing after the deadline.
Citations
- W3C WCAG 2.1 Recommendation - https://www.w3.org/TR/WCAG21/
- W3C: What is new in WCAG 2.1 - https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/
- W3C WCAG 2.2 Recommendation - https://www.w3.org/TR/WCAG22/
- W3C WCAG 2 FAQ (4.1.1 Parsing) - https://www.w3.org/WAI/standards-guidelines/wcag/faq/
- ADA.gov: Fact sheet on the Title II web rule - https://www.ada.gov/resources/2024-03-08-web-rule/
- Federal Register: Extension of Title II compliance dates (April 20, 2026) - https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web
- ETSI EN 301 549 V3.2.1 - https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf
Author
Mythili Raju
Blogs: 56
Mythili is a Community Contributor at TestMu AI with 3+ years of experience in software testing and marketing. She holds certifications in Automation Testing, KaneAI, Selenium, Appium, Playwright, and Cypress. At TestMu AI, she leads go-to-market (GTM) strategies, collaborates on feature launches, and creates SEO optimized content that bridges technical depth with business relevance. A graduate of St. Joseph’s University, Bangalore, Mythili has authored 35+ blogs and learning hubs on AI-driven test automation and quality engineering. Her work focuses on making complex QA topics accessible while aligning content strategy with product and business goals.
Reviewer
Shahzeb Hoda
Reviewer
Shahzeb Hoda is the Associate Director of Marketing and a Community Contributor at TestMu AI, leading strategic initiatives in developer marketing, content, and community growth. With 10+ years of experience in quality engineering, software testing, automation testing, and e-learning, he has authored and reviewed 70+ technical articles on software testing and automation. Shahzeb holds an M.Tech in Computer Science from BIT, Mesra, and is certified in Selenium, Cypress, Playwright, Appium, and KaneAI. He brings deep expertise in CI/CD pipeline automation, cross-browser testing, AI-driven testing practices, and framework documentation. On LinkedIn, he is followed by 3,700+ engineers, developers, DevOps professionals, tech leaders, and enthusiasts.
WCAG 2.1 FAQs
Did you find this page helpful?
More Related Blogs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests