Scan Your Website for WCAG Accessibility Issues
TestMu AI Accessibility Testing Agent Runs Automated WCAG Checks on Real Devices, and Screen Readers, Then Ties Each Fix to the Rule It Fails.
WCAG 2.2 Explained: Guidelines, New Success Criteria & Checklist
WCAG 2.2 explained: the four principles, A, AA, and AAA levels, the 9 new success criteria, a 55-item Level A and AA checklist, and which version laws require.
Last Updated on:
WCAG 2.2 is the version of the Web Content Accessibility Guidelines that the W3C currently recommends, and the one to audit against when you want a site that also satisfies WCAG 2.1 and 2.0.
This guide covers the four principles, the A, AA, and AAA levels, the nine success criteria added in 2.2, a full Level A and AA checklist, and which WCAG version US and EU rules actually reference.
TL;DR
WCAG 2.2 is the current W3C Recommendation of the Web Content Accessibility Guidelines, first published on 5 October 2023 and updated on 12 December 2024. It keeps every WCAG 2.1 success criterion except the removed 4.1.1 Parsing, and adds nine new ones covering focus visibility, dragging, target size, consistent help, redundant entry, and accessible authentication.
What Changed in WCAG 2.2?
- Nine new success criteria: Per the W3C "What's New in WCAG 2.2" summary, six apply at Level A or AA (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) and three at Level AAA (2.4.12, 2.4.13, 3.3.9).
- 4.1.1 Parsing removed: The W3C marks 4.1.1 Parsing as obsolete and removed in WCAG 2.2, and its WCAG 2 FAQ says to treat it as always satisfied for HTML or XML content under WCAG 2.0 and 2.1.
- 55 Level A and AA criteria: The W3C WCAG 2.2 Recommendation lists 31 Level A and 24 Level AA success criteria, which is the full set a page must pass to conform to WCAG 2.2 AA.
- Backward compatibility: The WCAG 2.2 Recommendation states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1, so one 2.2 AA audit also covers the older versions.
- ISO/IEC 40500:2025: The W3C WCAG overview states that ISO/IEC 40500:2025 is exactly the same as the October 2023 version of WCAG 2.2. A 2012 W3C press release records the earlier ISO/IEC 40500:2012 as WCAG 2.0.
How Do You Test Against WCAG 2.2?
Automated scans catch failures such as missing alt text, unlabeled fields, and low contrast, while keyboard and screen reader checks cover the rest. TestMu AI's accessibility testing platform supports WCAG 2.2 scans through its Accessibility DevTools extension and Selenium, Playwright, and Cypress automation.
What Is WCAG 2.2?
The Web Content Accessibility Guidelines (WCAG) are the W3C standard for making web content accessible to people with disabilities. According to the W3C WCAG 2 Overview, WCAG 2.2 has 13 guidelines, each with testable success criteria rated Level A, AA, or AAA.
WCAG testing is the process of checking a site against those success criteria, combining automated scans with manual review to find the accessibility issues that block real users. WCAG is the measurable standard behind the broader practice of web accessibility.
WCAG Versions: 2.0 vs 2.1 vs 2.2
Each WCAG 2 version keeps the success criteria of the one before it and adds new ones, with one exception: WCAG 2.2 removes 4.1.1 Parsing. Laws often name an older version, so it helps to know what each one covers.
| Version | W3C Recommendation | Level A and AA Criteria | What It Added | Referenced By |
|---|---|---|---|---|
| WCAG 2.0 | 11 December 2008 | 38 (25 A, 13 AA) | The original 12 guidelines under the four principles | Revised Section 508 Standards (A and AA); published as ISO/IEC 40500:2012 |
| WCAG 2.1 | 5 June 2018 | 50 (30 A, 20 AA) | 17 criteria for mobile, low vision, and cognitive needs, such as 1.3.4 Orientation and 1.4.10 Reflow | ADA Title II web rule (AA); EN 301 549 V3.2.1 |
| WCAG 2.2 | 5 October 2023 | 55 (31 A, 24 AA) | 9 criteria, such as 2.4.11 Focus Not Obscured (Minimum) and 2.5.8 Target Size (Minimum); removes 4.1.1 Parsing | The current W3C Recommendation; published as ISO/IEC 40500:2025 |
| WCAG 3.0 | Working Draft | Not final | A new conformance model, still in draft | Not referenced by any law yet |
What Are the Four Principles of WCAG?
The four principles of WCAG are Perceivable, Operable, Understandable, and Robust, usually shortened to POUR. Every guideline and success criterion sits under one of them.
- Perceivable - Users can perceive the content with at least one sense: text alternatives for images (1.1.1), captions for video (1.2.2), and enough color contrast (1.4.3).
- Operable - Every function works with a keyboard (2.1.1), users get enough time (2.2.1), and pointer targets are large enough to hit (2.5.8).
- Understandable - Pages declare their language (3.1.1), behave predictably (3.2.1), and help users avoid and fix input errors (3.3.1).
- Robust - Components expose their name, role, and value to assistive technology (4.1.2), and status messages are announced (4.1.3).
For test cases under each principle, see this breakdown of POUR principles in accessibility testing.
What Are the WCAG Conformance Levels?
WCAG has three conformance levels, and each one includes every requirement of the levels below it. The counts below come from the W3C WCAG 2.2 Recommendation.
- Level A - The minimum level, with 31 success criteria in WCAG 2.2, such as 1.1.1 Non-text Content and 2.1.1 Keyboard. Failing these leaves some users unable to use the page at all.
- Level AA - Adds 24 more criteria (55 in total), such as 1.4.3 Contrast (Minimum), which requires 4.5:1 for normal text and 3:1 for large text. AA is the level that the ADA Title II rule and Section 508 reference.
- Level AAA - The strictest level, such as 1.4.6 Contrast (Enhanced) at 7:1. The W3C notes that requiring AAA as a general policy for entire sites is not recommended, because some content cannot satisfy every AAA criterion.
For how the levels differ in practice and how to pick a target, read about WCAG conformance levels and their differences.
Note: Run manual and automated WCAG 2.2 tests online. Try TestMu AI Now!
What's New in WCAG 2.2?
WCAG 2.2 became a W3C Recommendation on 5 October 2023. The W3C summary of what's new in WCAG 2.2 lists 9 success criteria added since WCAG 2.1 and confirms that 4.1.1 Parsing is obsolete and removed.
| Criterion | Level | Requirement | What to Test |
|---|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A component with keyboard focus is not entirely hidden by author-created content. | Tab through pages with sticky headers, cookie banners, and chat widgets open. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused component is hidden by author-created content. | Same tab pass; any overlap of the focused element fails. |
| 2.4.13 Focus Appearance | AAA | The focus indicator is at least as large as a 2 CSS pixel thick perimeter of the component and changes by 3:1 contrast between focused and unfocused states. | Measure custom focus rings and compare focused and unfocused pixel colors. |
| 2.5.7 Dragging Movements | AA | Anything done by dragging can also be done with a single pointer without dragging. | Complete sliders, sortable lists, and map panning with clicks or taps only. |
| 2.5.8 Target Size (Minimum) | AA | Pointer targets are at least 24 by 24 CSS pixels, or spaced so a 24 pixel circle around each does not overlap another target. | Measure icon buttons, pagination, and inline controls, especially on mobile. |
| 3.2.6 Consistent Help | A | Help mechanisms repeated across pages (contact details, chat, self-help links) stay in the same relative order. | Compare help placement across page templates. |
| 3.3.7 Redundant Entry | A | Information already entered in the same process is auto-populated or available to select. | Walk through multi-step checkouts and sign-ups looking for repeated fields. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login steps do not require a cognitive function test, such as remembering a password or solving a puzzle, unless an alternative or assisting mechanism exists. | Confirm password managers, paste, and non-puzzle alternatives work on every login step. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Same as 3.3.8 without the object recognition and personal content exceptions. | Check that image-recognition CAPTCHAs are not the only path. |
If your site already passed a WCAG 2.1 AA audit, you do not need to start over. Run a delta pass on the six new Level A and AA criteria (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, and 3.3.8), and drop 4.1.1 Parsing findings from your reports, since the W3C WCAG 2 FAQ says to treat Parsing as always satisfied for HTML or XML content.
WCAG 2.2 Success Criteria Checklist (Level A and AA)
This checklist covers all 55 Level A and AA success criteria in the W3C WCAG 2.2 Recommendation, in document order, with 4.1.1 Parsing left out because WCAG 2.2 removes it. Linked criterion names open the TestMu AI rule doc for the automated check that covers that criterion; unlinked criteria need manual review.
| Success Criterion | Level | How to Test It |
|---|---|---|
| 1.1.1 Non-text Content | A | Meaningful images, icons, and image buttons have text alternatives; decorative images are hidden from assistive technology. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Prerecorded audio-only has a transcript; prerecorded video-only has a text or audio alternative. |
| 1.2.2 Captions (Prerecorded) | A | Prerecorded video with audio has accurate, synchronized captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Prerecorded video has audio description or a full text alternative. |
| 1.2.4 Captions (Live) | AA | Live video with audio has captions. |
| 1.2.5 Audio Description (Prerecorded) | AA | Prerecorded video has audio description of important visual content. |
| 1.3.1 Info and Relationships | A | Headings, lists, tables, and form labels are marked up in code, not only styled visually. |
| 1.3.2 Meaningful Sequence | A | DOM reading order matches visual order wherever order changes meaning. |
| 1.3.3 Sensory Characteristics | A | Instructions do not rely only on shape, size, position, or sound, such as "click the round button". |
| 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 user data, such as name and email, carry the correct autocomplete attribute. |
| 1.4.1 Use of Color | A | Color is not the only way information is shown, for example in links, charts, and error states. |
| 1.4.2 Audio Control | A | Audio that plays automatically for more than 3 seconds can be paused, stopped, or turned down independently. |
| 1.4.3 Contrast (Minimum) | AA | Text contrast is at least 4.5:1, or 3:1 for large text. |
| 1.4.4 Resize Text | AA | Text can be resized to 200% without loss of content or function. |
| 1.4.5 Images of Text | AA | Real text is used instead of images of text, except logos or where a specific presentation is essential. |
| 1.4.10 Reflow | AA | At a width of 320 CSS pixels, content reflows without two-dimensional scrolling or loss of information. |
| 1.4.11 Non-text Contrast | AA | Input borders, focus and state indicators, and meaningful graphics reach 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | AA | Nothing is cut off with line height 1.5, paragraph spacing 2, letter spacing 0.12, and word spacing 0.16 times the font size. |
| 1.4.13 Content on Hover or Focus | AA | Tooltips and popovers can be dismissed without moving focus, can be hovered, and stay until dismissed. |
| 2.1.1 Keyboard | A | Every function works with a keyboard alone. |
| 2.1.2 No Keyboard Trap | A | Focus can always move away from any component using the keyboard, including modals and embedded players. |
| 2.1.4 Character Key Shortcuts | A | Single-character shortcuts can be turned off, remapped, or only work when the component has focus. |
| 2.2.1 Timing Adjustable | A | Time limits can be turned off, adjusted, or extended, with a warning that gives at least 20 seconds to extend. |
| 2.2.2 Pause, Stop, Hide | A | Auto-starting moving, blinking, or scrolling content lasting more than five seconds can be paused, stopped, or hidden. |
| 2.3.1 Three Flashes or Below Threshold | A | Nothing flashes more than three times in any one second period, unless the flash is below the general and red flash thresholds. |
| 2.4.1 Bypass Blocks | A | A skip link or landmarks let users bypass repeated navigation. |
| 2.4.2 Page Titled | A | Each page has a title element that describes its topic or purpose. |
| 2.4.3 Focus Order | A | Tab order follows a sequence that preserves meaning, including after dialogs open and close. |
| 2.4.4 Link Purpose (In Context) | A | Each link's purpose is clear from its text or surrounding context; no bare "click here". |
| 2.4.5 Multiple Ways | AA | Pages can be found in more than one way, such as navigation, search, or a sitemap, except steps in a process. |
| 2.4.6 Headings and Labels | AA | Headings and labels describe the topic or purpose of the content they introduce. |
| 2.4.7 Focus Visible | AA | Every keyboard-focused element shows a visible focus indicator. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused element is never entirely hidden behind sticky headers, banners, or other author content. |
| 2.5.1 Pointer Gestures | A | Multipoint or path-based gestures, such as pinch or swipe, have a single-pointer alternative. |
| 2.5.2 Pointer Cancellation | A | Actions fire on pointer up, or can be aborted or undone, so accidental presses can be cancelled. |
| 2.5.3 Label in Name | A | A control's accessible name contains its visible label text, so voice users can say what they see. |
| 2.5.4 Motion Actuation | A | Functions triggered by shaking or tilting have a UI alternative and can be disabled. |
| 2.5.7 Dragging Movements | AA | Drag actions can also be completed with single clicks or taps. |
| 2.5.8 Target Size (Minimum) | AA | Pointer targets are at least 24 by 24 CSS pixels or have enough spacing, with the listed exceptions. |
| 3.1.1 Language of Page | A | The html element has a valid lang attribute. |
| 3.1.2 Language of Parts | AA | Passages in another language carry their own lang attribute. |
| 3.2.1 On Focus | A | Moving focus to a component does not trigger a change of context, such as a page navigation. |
| 3.2.2 On Input | A | Changing a setting, such as a select option, does not cause an unannounced change of context. |
| 3.2.3 Consistent Navigation | AA | Navigation repeated across pages appears in the same relative order. |
| 3.2.4 Consistent Identification | AA | Components with the same function, such as search or print icons, are labeled the same way on every page. |
| 3.2.6 Consistent Help | A | Repeated help mechanisms, such as contact links or chat, stay in the same relative order across pages. |
| 3.3.1 Error Identification | A | Submit invalid data; each detected error is identified and described to the user in text. |
| 3.3.2 Labels or Instructions | A | Every input has a visible label or instructions; placeholder text is not the only label. |
| 3.3.3 Error Suggestion | AA | When a fix for an input error is known, the error message suggests it. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Legal, financial, or data-changing submissions are reversible, checked for errors, or confirmed before final submission. |
| 3.3.7 Redundant Entry | A | Information already entered in the same process is auto-populated or available to select. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login does not depend on remembering, transcribing, or solving a puzzle without an alternative such as paste or a password manager. |
| 4.1.2 Name, Role, Value | A | Custom controls expose their name, role, state, and value to assistive technology. |
| 4.1.3 Status Messages | AA | Status updates, such as "added to cart" or search result counts, are announced without moving focus. |
A passing automated check on a linked criterion is not full conformance on its own. Rules like 1.1.1 can confirm that alt text exists, but only a person can judge whether it describes the image, so pair each scan with the manual checks in the next sections.
Which WCAG Version Is Required by Law?
WCAG is the technical standard; laws and regulations decide which version applies to you. The main rules reference different versions:
- ADA Title II (US state and local governments) - The Department of Justice ADA Title II web rule sets WCAG 2.1 Level AA as the technical standard for web content and mobile apps.
- Section 508 (US federal agencies) - Requirement E205.4 of the Revised 508 Standards requires electronic content to conform to WCAG 2.0 Level A and Level AA. See this guide to Section 508 compliance for scope and exceptions.
- EN 301 549 (EU) - ETSI's EN 301 549 V3.2.1, published in 2021, references WCAG 2.1 conformance requirements, and the W3C WCAG 2 Overview notes that the 2026 version of EN 301 549 uses WCAG 2.2.
Is WCAG 2.1 or 2.2 Required?
The US rules above name WCAG 2.1 AA (ADA Title II) and WCAG 2.0 AA (Section 508), not 2.2. Testing against WCAG 2.2 AA still satisfies them: the WCAG 2.2 Recommendation states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and 2.1, and that the W3C intends 2.2 to provide an alternate means of conformance for policies that require 2.0 or 2.1.
Is WCAG Mandatory in the USA?
For state and local governments and federal agencies, yes, through the ADA Title II rule and Section 508. The ada.gov page for the Title II rule applies it to state and local governments and their contractors; it does not set a WCAG version for private businesses under ADA Title III.
When Must State and Local Governments Meet ADA Title II Web Rules?
According to ada.gov, 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 conformance by April 26, 2027.
- Under 50,000 and special district governments - The same standard by April 26, 2028.
Conformance does not end at the deadline: new and updated pages must keep meeting WCAG 2.1 AA, which is why teams add accessibility checks to every release.
How to Test a Website Against WCAG 2.2
A WCAG 2.2 audit combines automated scans for machine-checkable criteria with manual checks for everything that needs judgment. For the full process from scoping to reporting, follow this accessibility testing guide; the short version is below.
- Scope - Pick representative templates and key flows such as login, search, checkout, and forms, and set WCAG 2.2 Level AA as the target.
- Scan - Run automated accessibility testing tools, or an online accessibility checker for WCAG for a quick check, to catch missing alt text, unlabeled fields, and failing contrast ratios.
- Keyboard - Tab through every flow and check 2.1.1, 2.1.2, 2.4.3, 2.4.7, and 2.4.11 together: reachable controls, no traps, logical order, and a visible, unobscured focus indicator.
- Screen reader - Use screen reader accessibility testing to confirm names, roles, form errors, and status messages are announced (4.1.2, 3.3.1, 4.1.3).
- New 2.2 criteria - Measure target sizes on small screens as part of checking mobile app accessibility, try drag interactions with taps only, and walk through login and multi-step forms for 3.3.7 and 3.3.8.
- Color, zoom, and reflow - Check color-only cues with a color blindness simulator, resize text to 200%, and view pages at 320 CSS pixels wide.
- Fix and retest - Fix failures that block key tasks first, retest after every release, and keep a web accessibility checklist next to the 55-item table above.
Example: Automated Scan of the W3C Before and After Demo
The W3C publishes a Before and After Demonstration: one website built with accessibility barriers and a repaired version of the same site. For this guide, both home pages were scanned with axe-core 4.10.2 in Chrome on the TestMu AI cloud on October 5, 2026, using the WCAG 2.0, 2.1, and 2.2 Level A and AA rule sets.
| Page | Rules failed | Elements affected | Main failures |
|---|---|---|---|
| Before (inaccessible) | 6 | 46 | 33 images without alt text (1.1.1), 7 links without names (2.4.4), missing page language (3.1.1), a select without a label, 2 contrast failures, 2 small targets |
| After (repaired) | 1 | 2 | 2 targets under 24 by 24 pixels (2.5.8, new in WCAG 2.2) |
The repaired page cleared every WCAG 2.0 and 2.1 rule axe checks, but it still failed Target Size (Minimum), a criterion added in WCAG 2.2 after the demo was built. Content that met an older version needs a fresh pass against 2.2.
The scan also left 24 contrast checks on the repaired page as "needs review", because text over images and gradients cannot be measured automatically. The W3C's own evaluation of the inaccessible page lists problems no scanner can detect, such as unclear link purpose and confusing reading order, which is why manual testing stays part of every WCAG audit.
How to Run WCAG 2.2 Tests With TestMu AI
TestMu AI covers both halves of a WCAG audit: browser-based scanning and manual checks during development and QA, and automated scans inside existing test suites in CI.
TestMu AI Accessibility DevTools
The TestMu AI Accessibility DevTools Chrome extension runs axe-core based scans on live pages and lists each violation with its WCAG reference.
- On-demand scans - Scan any page from the DevTools panel and click an issue to locate the affected element in the DOM.
- Keyboard Scan - Validate keyboard-only navigation, focus order, and keyboard traps that DOM-only scanning cannot fully evaluate.
- Screen reader testing - Test with NVDA, JAWS, VoiceOver, and TalkBack in the cloud without local setup.
To get started, refer to the TestMu AI Accessibility DevTools documentation.
TestMu AI Accessibility Automation
Accessibility Automation adds WCAG scans to Selenium, Playwright, and Cypress suites running on the TestMu AI cloud, so every build is checked without a separate pipeline step.
- Framework support - Selenium (Chrome and Edge), Playwright (Chrome only; bundled pw-chromium is not supported), and Cypress, plus TestNG, JUnit 5, NUnit, Robot Framework, and Cucumber.
- Accessibility MCP Server - Exposes accessibility analysis as tools in AI code editors such as Cursor and VS Code, so you can find and fix issues where you write code.
To begin, visit the TestMu AI Accessibility Automation documentation.
WCAG 3.0 Status
WCAG 3 is still a Working Draft, with the latest draft published in September 2026. The W3C WCAG 3 Introduction calls it an incomplete draft that is not expected to be a completed standard for a few more years, and says WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. WCAG 2.2 is the version to test against today.
Conclusion
Start with the six new WCAG 2.2 Level A and AA criteria, since they are the gap between an existing 2.1 AA audit and 2.2 AA. Then work through the 55-item checklist above, scanning the linked criteria automatically and covering the rest with keyboard and screen reader checks.
To run that first scan, install TestMu AI Accessibility DevTools and test one key flow, such as login or checkout, before scaling the checks into your CI suite.
Is your app accessible to everyone? TestMu AI's Accessibility Testing finds WCAG issues across web and mobile before release.
Citations
- WCAG 2 FAQ (4.1.1 Parsing) - https://www.w3.org/WAI/standards-guidelines/wcag/faq/
- W3C press release on ISO/IEC 40500:2012 (WCAG 2.0) - https://www.w3.org/2012/07/wcag2pas-pr.html
Author
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
Rahul Mishra is a Lead Member of Technical Staff at TestMu AI, leading frontend engineering and accessibility testing across the quality engineering platform. He mentors frontend engineers, runs code reviews and sprint planning, optimizes React.js rendering performance, and makes product features accessible to users with disabilities through WCAG and ADA-compliant accessibility audits. He brings 10+ years of experience across React.js, VueJS, TypeScript, Swift, Objective-C, and AWS, with earlier work as a Technical Lead at VectoScalar Technologies. Rahul holds a B.E. in Information Technology.
WCAG 2.2 FAQs
Did you find this page helpful?
More Related Learning Hubs
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



















