What is the difference between WCAG 2.1 and WCAG 2.2?

The main difference is that WCAG 2.2 builds on WCAG 2.1 by adding nine new accessibility success criteria, with particular emphasis on keyboard navigation, users with low vision, people with cognitive disabilities, and making websites easier to interact with. Both are versions of the Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C). WCAG 2.1 was published in 2018, while WCAG 2.2 was published in October 2023. [WCAG 2 Overview | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/)[Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/?COS_TEMPLATE_INTENT=NEWSLETTER) ## 1. WCAG 2.1 vs. WCAG 2.2 at a glance | Feature | WCAG 2.1 | WCAG 2.2 | | --- | --- | --- | | Primary focus | Accessibility across web, mobile, low vision, and cognitive needs | Builds on 2.1 with additional requirements for usability and accessibility | | New success criteria in that version | 17 added over WCAG 2.0 | 9 added over WCAG 2.1 | | Keyboard navigation | Existing keyboard accessibility requirements | Adds requirements for visible focus and focus not being obscured | | Touch and pointer interaction | Existing requirements | Adds minimum target-size and dragging alternatives | | Login and authentication | Existing accessibility requirements | Adds requirements to reduce cognitive barriers during authentication | | Forms and help | Existing accessibility requirements | Adds consistent help and reduced redundant data entry | | Backward compatibility | Builds on WCAG 2.0 | Conformance also satisfies WCAG 2.1 and 2.0 | Source: W3C's [WCAG overview](https://www.w3.org/WAI/standards-guidelines/wcag/) and [WCAG 2.2 changes](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/). [WCAG 2 Overview | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/)[What's New in WCAG 2.2 | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) ## 2. What exactly changed in WCAG 2.2? WCAG 2.2 introduced nine new success criteria. Here are the practical differences that matter most. 1. Better keyboard focus visibility WCAG 2.2 adds requirements to ensure focused elements are not entirely hidden behind sticky headers, footers, or other author-created content (AA). It also defines stronger focus-indicator requirements at AAA. Example: When someone tabs to a button, they can see which button is selected. 2. Larger, easier-to-use interactive targets WCAG 2.2 introduces a minimum target-size criterion at AA: generally, interactive targets must be at least 24 × 24 CSS pixels, subject to specified exceptions. Example: Small icons and buttons become easier to select for users with motor impairments. 3. Alternatives to dragging WCAG 2.2 requires a single-pointer alternative to dragging movements at AA, unless an exception applies. Example: Users can move a list item using buttons instead of dragging it with a mouse or finger. 4. More accessible authentication WCAG 2.2 adds requirements that reduce reliance on cognitive-function tests, such as remembering or transcribing information, for login. Example: A site supports password managers, copy-and-paste, or an alternative authentication method rather than forcing users to solve a memory-based challenge. 5. Less repeated data entry WCAG 2.2 adds a requirement to make information previously entered in the same process available again, with specified exceptions. Example: A checkout process reuses an address already provided instead of asking the user to type it again. 6. More consistent access to help WCAG 2.2 requires repeated help mechanisms to appear in the same relative order across pages, unless the user initiates a change. Example: Contact details, help links, or a support chat mechanism are consistently placed throughout a website. These additions are defined in the official [WCAG 2.2 specification](https://www.w3.org/TR/WCAG22/) and [W3C explanation of the new criteria](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/). [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/?COS_TEMPLATE_INTENT=NEWSLETTER)[What's New in WCAG 2.2 | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) ## 3. Are the existing WCAG 2.1 requirements different in WCAG 2.2? Almost all existing requirements remain unchanged. WCAG 2.2 adds new criteria rather than rewriting the existing WCAG 2.1 criteria. There is one technical exception: Success Criterion 4.1.1, Parsing, was marked obsolete and removed from WCAG 2.2. If a contract or policy explicitly requires WCAG 2.1, you may still need to test and report against that criterion. [WCAG 2 Overview | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/)[Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/?COS_TEMPLATE_INTENT=NEWSLETTER) WCAG 2.2 is backward-compatible: a website that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0. ## 4. Which standard should you use? My recommendation is to target WCAG 2.2 Level AA for a new website, redesign, or accessibility remediation project, unless a specific law, contract, or regulatory requirement dictates otherwise. WCAG conformance has three levels: - Level A: The foundational accessibility requirements. - Level AA: The commonly used target for accessibility policies and compliance. - Level AAA: More stringent requirements that are not generally expected to be met in full across an entire website. For an existing site that already meets WCAG 2.1 AA, you do not necessarily need to rebuild it. Instead, perform a gap analysis against the nine new WCAG 2.2 criteria and fix the issues that arise. One important distinction: the latest WCAG version and the legally required version are not always the same. Check the applicable jurisdiction, regulation, and contract before determining your formal compliance target. For implementation, start with the [W3C WCAG 2.2 Quick Reference](https://www.w3.org/WAI/WCAG22/quickref/).

Here’s a clear breakdown of the differences between **WCAG 2.1** and **WCAG 2.2**: ## 📅 Publication Timeline * **WCAG 2.1**: Published June 5, 2018 * **WCAG 2.2**: Published October 5, 2023 (current W3C Recommendation) ## 🔑 Key Differences Aspect| WCAG 2.1| WCAG 2.2 ---|---|--- **Total Success Criteria**| 78| 86 (adds 9, removes 1) **Removed Criteria**| None| 4.1.1 Parsing (obsolete due to modern HTML5/browser handling) **New Criteria**| None| 9 new success criteria **Focus Areas**| Mobile accessibility, low vision, cognitive disabilities| Cognitive & learning disabilities, motor impairments, sighted keyboard users **Backward Compatibility**| Superseded| Backward-compatible (meeting 2.2 = meeting 2.1 & 2.0) ## 🆕 New Success Criteria in WCAG 2.2 ### Level A * **3.2.6 Consistent Help** – Help mechanisms (like contact links or chat) must appear in the same relative location across pages. * **3.3.7 Redundant Entry** – Users shouldn’t have to re-enter information already provided; auto-fill or selection should be available. ### Level AA * **2.4.11 Focus Not Obscured (Minimum)** – Keyboard focus must not be hidden behind sticky headers, banners, or overlays. * **2.5.7 Dragging Movements** – Any dragging action must have a single-pointer alternative (e.g., click/tap). * **2.5.8 Target Size (Minimum)** – Interactive targets must be at least 24×24 CSS pixels (with exceptions). * **3.3.8 Accessible Authentication (Minimum)** – Authentication must not rely solely on cognitive function tests (like remembering passwords or solving puzzles). ### Level AAA * **2.4.12 Focus Not Obscured (Enhanced)** – Focused elements must not be hidden at all. * **2.4.13 Focus Appearance** – Focus indicators must meet minimum size and contrast requirements. * **3.3.9 Accessible Authentication (Enhanced)** – Stronger requirements for accessible authentication beyond the AA level. ## ⚖️ Legal & Practical Notes * Many laws (like the EU’s EN 301 549 and U.S. DOJ ADA Title II) still reference **WCAG 2.1 AA**, but conforming to **WCAG 2.2 AA** automatically satisfies 2.1 AA. * Migrating from 2.1 → 2.2 is additive: you only need to meet the 9 new criteria (6 at A/AA, 3 at AAA). ✅ **In short:** WCAG 2.2 is a superset of WCAG 2.1, with 9 new criteria (mainly improving accessibility for users with cognitive, motor, and keyboard navigation needs) and the removal of one outdated rule. If you’re already compliant with 2.1, upgrading to 2.2 means addressing these additional requirements. [WCAG 2.1 vs 2.2: What Changed & How to Migrate](https://accessibility.build/guides/wcag-2-1-vs-2-2)[WCAG 2.2 vs 2.1: 9 New Criteria, 1 Removed - Full Comparison [2026]](https://web-accessibility-checker.com/en/blog/wcag-2-2-vs-2-1-differences)[WCAG 2.2 vs 2.1 - Complete Comparison of Accessibility Standards | TheWCAG | TheWCAG](https://www.thewcag.com/wcag-2-2-vs-2-1)[WCAG 2.1 vs 2.2: what changed, in one table | wcag22aa.org](https://www.wcag22aa.org/wcag-2-1-vs-2-2/)[WCAG 2.1 vs 2.2: what actually changed](https://wcagc.com/blog/wcag-2-1-vs-2-2) Would you like me to create a **practical checklist** of the 6 new Level A/AA criteria so you can quickly see what’s needed to upgrade from WCAG 2.1 AA to 2.2 AA?

The **Web Content Accessibility Guidelines (WCAG)** are developed by the World Wide Web Consortium (W3C) to define how to make web content more accessible to people with disabilities. **WCAG 2.2** is an extension of **WCAG 2.1** , rather than a complete rewrite. It preserves the core structure of both 2.0 and 2.1 - meaning it continues to rely on the four **POUR** principles (Perceivable, Operable, Understandable, Robust). [WCAG 2.1 Vs WCAG 2.2: What's Changed and Why It Matters](https://reciteme.com/us/news/wcag-2-1-vs-wcag-2-2/#:~:text=These%20principles%20remain%20the%20foundation%20of%20accessibility%2C,most%20notable%20changes%20in%20WCAG%202.2%20include%3A)[What Is the Difference Between WCAG 2.2 and WCAG 2.1? - TestParty](https://testparty.ai/blog/wcag-22-vs-21-comparison#:~:text=New%20criteria%20primarily%20address%20cognitive%20disabilities%2C%20mobile,specific%20success%20criteria%20additions%20and%20one%20removal.) The primary difference between the two versions is that **WCAG 2.2 adds 9 new success criteria** (specifically improving experiences for mobile users, people with low vision, motor disabilities, and cognitive/learning difficulties) and **removes 1 outdated criterion**. [What Is the Difference Between WCAG 2.2 and WCAG 2.1? - TestParty](https://testparty.ai/blog/wcag-22-vs-21-comparison) ### Key Comparison Summary Metric| WCAG 2.1| WCAG 2.2 ---|---|--- **Release Year**| 2018| 2023 **Total Success Criteria**| 78| 87 **Backward Compatible**| Yes (includes 2.0)| Yes (includes 2.1 and 2.0) **Primary Focus Areas**| Mobile accessibility, low vision, and general web inclusion.| Cognitive accessibility, mobile/touch interactions, and keyboard navigation. ### The 9 New Success Criteria in WCAG 2.2 The additions in WCAG 2.2 target specific user friction points that were not fully addressed in 2.1: 1. **Focus Not Obscured (Minimum) (Level AA - 2.4.11):** When a component receives keyboard focus, it must not be completely hidden by author-created content (like a sticky header or cookie banner). [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=low%20vision%20%7C%20When%20an%20element%20receives,Focus%20Appearance%20%7C%20AAA%20%7C%20Low%20vision%3B) 2. **Focus Not Obscured (Enhanced) (Level AAA - 2.4.12):** Takes it a step further - no part of the focused component can be obscured by sticky/floating elements. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=11\(opens%20in%20a%20new%20tab\)%20requires%20that%2C,occasionally%20be%20obscured%20by%20other%20web%20elements.) 3. **Focus Appearance (Level AAA - 2.4.13):** Focus indicators (the outline around buttons/links) must meet specific size and high-contrast requirements so they are exceptionally easy to see. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=attention%20limitations%20%7C%20The%20focused%20element%20is,Dragging%20Movements%20%7C%20AA%20%7C%20Motor%20impairments%3B) 4. **Dragging Movements (Level AA - 2.5.7):** Any action that requires dragging (such as sliders, maps, or reordering items) must have a simple single-pointer alternative, like tapping an arrow or button. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=*%20Dragging%20has%20an%20alternative%20\(2.5.%207\)%3A,targets%20aren't%20easy%20to%20hit%20by%20accident.) 5. **Target Size (Minimum) (Level AA - 2.5.8):** Clickable elements (like buttons, links, and form inputs) must be at least **24x24 CSS pixels** , or have sufficient spacing to prevent accidental activation on mobile devices. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=users%20of%20alternative%20input%20devices%20%7C%20Any,have%20enough%20spacing%20to%20prevent%20accidental%20activation.) 6. **Consistent Help (Level A - 3.2.6):** If help mechanisms (like contact info, FAQs, or chat widgets) appear across multiple pages, they must appear in the same relative order/location. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=*%20Help%20is%20consistent%20\(3.2.%206\)%3A%20Place,the%20same%20process%2C%20unless%20re%2Dentry%20is%20essential.) 7. **Redundant Entry (Level A - 3.3.7):** Users should not be forced to re-enter the exact same information earlier in a multi-step form process; it must be auto-populated or selectable. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=users%20of%20alternative%20input%20devices%20%7C%20Any,have%20enough%20spacing%20to%20prevent%20accidental%20activation.) 8. **Accessible Authentication (Minimum) (Level AA - 3.3.8):** Logins must not rely solely on cognitive tests (such as solving puzzles or memorizing complex passwords/transcribing codes) unless an alternative method (like password managers, email links, or biometrics) is provided. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=%7C%20%7C%203.3.7%20Redundant%20Entry%20%7C%20A,unless%20an%20alternative%20or%20assistance%20is%20provided.) 9. **Accessible Authentication (Enhanced) (Level AAA - 3.3.9):** A stricter version of 3.3.8, banning object recognition or user-uploaded images as the sole login method. [What's New in WCAG 2.2: The 9 New Success Criteria Explained](https://www.audioeye.com/post/whats-new-with-wcag-2-2/#:~:text=%7C%20%7C%203.3.8%20Accessible%20Authentication%20\(Minimum\)%20%7C,images\)%20can't%20be%20used%20for%20authentication.%20%7C) ### The Removed Criterion: 4.1.1 Parsing WCAG 2.2 officially **removed Success Criterion 4.1.1 Parsing**. [What Is the Difference Between WCAG 2.2 and WCAG 2.1? - TestParty](https://testparty.ai/blog/wcag-22-vs-21-comparison#:~:text=Key%20Takeaways.%20This%20comparison%20covers%20every%20difference,cognitive%20disabilities%2C%20mobile%20users%2C%20and%20keyboard%20navigation.) * **Why?** In earlier web days, this rule checked that HTML code was perfectly formed (proper tag nesting, complete start/end tags, no duplicate IDs). * Modern web browsers and assistive technologies now handle minor parsing and syntax errors gracefully on their own. Because this rule no longer provided a practical barrier for users, it was deprecated. [What Is the Difference Between WCAG 2.2 and WCAG 2.1? - TestParty](https://testparty.ai/blog/wcag-22-vs-21-comparison#:~:text=WCAG%202.2%20removes%204.1.%201%20Parsing%20because,parsing%20errors%20are%20no%20longer%20WCAG%20failures.)[Understanding the Evolution: WCAG 2.1 vs WCAG 2.2 - Siteimprove](https://www.siteimprove.com/blog/wcag-21-vs-wcag-22/#:~:text=6\)%20stops%20users%20from%20playing%20hide%2Dand%2Dseek%20with,markup%20rather%20than%20doing%20their%20own%20parsing.) ### Should you aim for WCAG 2.1 or WCAG 2.2? **You should aim for WCAG 2.2 (specifically Level AA compliance).** Because WCAG 2.2 is entirely backward compatible, any website that conforms to WCAG 2.2 automatically meets WCAG 2.1 and 2.0 requirements. Building your site to meet 2.2 future-proofs your digital properties against changing legal frameworks and ensures a smoother, less frustrating user experience for everyone. [What Is the Difference Between WCAG 2.2 and WCAG 2.1? - TestParty](https://testparty.ai/blog/wcag-22-vs-21-comparison#:~:text=WCAG%202.2%20removes%201%20criterion%20\(4.1.1%20Parsing\),to%202.1%20and%202.0.%20Overview%20of%20Changes.)[WCAG 2.1 Vs WCAG 2.2: What's Changed and Why It Matters](https://reciteme.com/us/news/wcag-2-1-vs-wcag-2-2/#:~:text=Legal%20alignment%20%E2%80%93%20many%20regions%20are%20updating,practices%20evolve.%20Accessibility%20is%20an%20ongoing%20journey%3B) Would you like help auditing a specific part of your website (such as form inputs, focus indicators, or mobile touch targets) against the WCAG 2.2 standards?

The **Web Content Accessibility Guidelines (WCAG)** version 2.2 builds directly upon WCAG 2.1, maintaining the foundational POUR framework (Perceivable, Operable, Understandable, and Robust). [What's New in WCAG 2.2 | Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/)[WCAG 2.1 Vs WCAG 2.2: What's Changed and Why It Matters](https://reciteme.com/us/news/wcag-2-1-vs-wcag-2-2/)[Understanding the Evolution: WCAG 2.1 vs WCAG 2.2](https://www.siteimprove.com/blog/wcag-21-vs-wcag-22/) WCAG 2.2 includes all prior success criteria from WCAG 2.1 (with one major exception), adds **9 new success criteria** , and focuses heavily on improving accessibility for mobile users, people with cognitive disabilities, and individuals with low vision. [Siteimprove +1] * * * Key Differences at a Glance * * **Total Success Criteria:** WCAG 2.1 has 78 success criteria, while WCAG 2.2 adds 9 new ones (totaling 87, minus the deprecated one). [W3C +2] * **Removed/Obsolete Rule:** WCAG 2.2 officially **deprecated and removed criteria 4.1.1 (Parsing)** , finding it obsolete due to modern browsers and assistive technologies handling minor HTML parsing errors automatically. [W3C +1] * **Backward Compatibility:** WCAG 2.2 is fully backward-compatible. If a site complies with WCAG 2.2, it automatically meets WCAG 2.1 and 2.0 (except for the retired 4.1.1 rule). [W3C] * * * * The 9 New Success Criteria in WCAG 2.2 The new criteria address gaps in mobile interaction, cognitive accessibility, and visual focus indicators: * * _2.4.11 Focus Not Obscured (Minimum) (Level AA):_ Ensures that when an item receives keyboard focus, it is not entirely hidden by author-created content (like sticky headers or cookie banners). * _2.4.12 Focus Not Obscured (Enhanced) (Level AAA):_ A stricter version ensuring no part of the focused element is obscured by other content. * _2.4.13 Focus Appearance (Level AAA):_ Sets specific minimum requirements for the size and contrast of keyboard focus indicator outlines. * _2.5.7 Dragging Movements (Level AA):_ Requires any function that uses a dragging movement (like a slider or reordering list) to have a single-pointer alternative (like simple click/tap buttons). * _2.5.8 Target Size (Minimum) (Level AA):_ Requires interactive touch targets (links, buttons) to be at least 24 × 24 pixels, or have enough spacing around them so they aren't accidentally mis-clicked. * _3.2.6 Consistent Help (Level A):_ If a website provides help mechanisms (such as a phone number, support link, or chat widget) across multiple pages, they must appear in the same relative order. * _3.3.7 Redundant Entry (Level AA):_ Users should not have to re-enter information they already provided earlier in the same user session (unless it's for security verification). * _3.3.8 Accessible Authentication (Minimum) (Level AA):_ Logins and authentication processes cannot rely on cognitive memory tests (like solving a puzzle or transcribing a code sent via memory), unless an alternative cognitive-free method is provided. * _3.3.9 Accessible Authentication (Enhanced) (Level AAA):_ A stricter version eliminating cognitive function tests completely from all authentication sequences. [W3C +2] * You can review the full technical documentation directly on the official [W3C WAI What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) page. [W3C] Would you like help **auditing your website** against these new criteria, or do you need recommendations on **how to fix specific WCAG 2.2 errors** like tap target sizing or authentication?

WCAG 2.2 adds nine success criteria to WCAG 2.1, with updates addressing areas such as focus visibility, dragging movements, target size, and accessible authentication. Existing criteria are unchanged, except that 2.2 removes 4.1.1 Parsing; WCAG 2.2 is backward-compatible with 2.1.([w3.org][1])([w3.org][2])([w3c.github.io][3]) [1]: https://www.w3.org/WAI/standards-guidelines/wcag/faq/ "WCAG 2 FAQ | Web Accessibility Initiative (WAI) - W3C" [2]: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/ "What's New in WCAG 2.2 | Web Accessibility Initiative (WAI) - W3C" [3]: https://w3c.github.io/wcag/guidelines/22/ "Web Content Accessibility Guidelines (WCAG) 2.2"