WCAG 2.2 Explained: What Changed and Why It Matters
The Web Content Accessibility Guidelines (WCAG) 2.2 became a W3C Recommendation (opens in new tab) on October 5, 2023, marking the latest evolution of the world's most widely adopted web accessibility standard. Whether you are a developer, designer, business owner, or compliance officer, understanding what changed in WCAG 2.2 is essential for keeping your website accessible and legally compliant.
In October 2025, WCAG 2.2 was also approved as the international standard ISO/IEC 40500:2025 (opens in new tab), so the same text now carries ISO status.
A Quick Background on WCAG
WCAG is developed by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI) (opens in new tab). The guidelines provide a shared, internationally recognized standard for making web content accessible to people with disabilities. WCAG is organized around four principles (Perceivable, Operable, Understandable, and Robust, known as POUR) and uses three conformance levels: A (minimum), AA (recommended), and AAA (aspirational).
WCAG 1.0 came out in 1999. WCAG 2.0 was published in 2008 and remained the primary standard for a decade. WCAG 2.1, published in 2018, added 17 new success criteria focused on mobile accessibility, low vision, and cognitive disabilities. Now, WCAG 2.2 builds on that foundation with nine additional success criteria.
A few examples show how the levels differ. Level A covers the basics, such as text alternatives for images (SC 1.1.1), keyboard access to every function (SC 2.1.1), and descriptive page titles (SC 2.4.2). Level AA adds requirements such as 4.5:1 text contrast (SC 1.4.3), text that resizes to 200% without breaking (SC 1.4.4), a visible focus indicator (SC 2.4.7), and consistent navigation (SC 3.2.3). Level AAA goes further, with 7:1 contrast (SC 1.4.6), sign language for prerecorded audio (SC 1.2.6), and a lower reading level (SC 3.1.5). Most laws and contracts that name a level ask for AA.
Each new version of WCAG is backward compatible. This means that a website conforming to WCAG 2.2 also conforms to WCAG 2.1 and 2.0. This backward compatibility is intentional and allows organizations to adopt the latest version without losing credit for work already done under earlier versions.
What Changed from WCAG 2.1 to 2.2?
WCAG 2.2 makes two types of changes: it adds nine new success criteria, and it retires one existing criterion. Here is a summary of each change and why it matters.
Criterion Removed: 4.1.1 Parsing
WCAG 2.2 marks Success Criterion 4.1.1 Parsing as obsolete. This criterion previously required that HTML be well-formed with unique IDs, proper nesting, and complete start/end tags. It was rendered obsolete because modern browsers and assistive technologies are now robust enough to handle minor parsing errors gracefully. The issues that 4.1.1 was designed to catch are now better addressed by other criteria and by browsers themselves. This does not mean sloppy HTML is acceptable. Valid, semantic HTML remains important for accessibility, but the specific parsing requirements are no longer a separate conformance check.
Nine New Success Criteria
Focus Not Obscured (Minimum)
Level AAWhen an element receives keyboard focus, it must not be entirely hidden by other author-created content, such as sticky headers, cookie banners, or chat widgets. At least part of the focused element must remain visible. This addresses a common frustration for keyboard users who tab to a focused element only to find it completely obscured by a fixed-position banner.
Focus Not Obscured (Enhanced)
Level AAAA stricter version of 2.4.11. The focused element must be fully visible, with no part of it hidden by other content. This is a Level AAA criterion, so it is aspirational for most organizations, but pursuing it leads to a significantly better keyboard navigation experience.
Focus Appearance
Level AAAThe keyboard focus indicator must be sufficiently visible. It needs a minimum area (at least as large as a 2px perimeter around the element) and a contrast ratio of at least 3:1 between the focused and unfocused states. This criterion ensures that focus indicators are not just present but actually usable by people with low vision.
Dragging Movements
Level AAAny functionality that requires a dragging movement (such as drag-and-drop reordering, slider controls, or map panning) must also be achievable through a single-pointer action without dragging. This benefits users with motor impairments who may have difficulty performing sustained dragging motions. For example, a sortable list should offer up/down buttons as an alternative to drag-and-drop.
Target Size (Minimum)
Level AAInteractive targets must be at least 24 by 24 CSS pixels (opens in new tab) in size. Small touch or click targets are a significant barrier for users with motor impairments, tremors, or limited dexterity, and the problem is most common on mobile devices.
The criterion lists five exceptions (opens in new tab):
- Spacing: a smaller target passes if a 24 px circle centered on it does not overlap another target or another small target's circle.
- Equivalent: the same function is available through another control on the same page that meets the size.
- Inline: the target sits in a sentence, or its size is set by the line height of the surrounding text.
- User agent control: the browser sets the size and the author has not changed it.
- Essential: the specific presentation is essential or legally required.
Consistent Help
Level AIf a website provides help mechanisms (contact information, live chat, FAQ links, self-help options), these mechanisms must appear in the same relative order across all pages. Users with cognitive disabilities rely on predictable patterns to navigate websites and find help when they need it. Consistent placement reduces cognitive load and prevents users from becoming lost or frustrated.
Redundant Entry
Level AInformation that a user has previously entered or provided during a multi-step process must be auto-populated or available for selection, unless re-entering it is essential (e.g., for security confirmation). This reduces the cognitive and motor burden on users who have difficulty remembering or re-typing information. Common examples include shipping/billing address forms where the billing address should auto-populate from the shipping address.
Accessible Authentication (Minimum)
Level AAAuthentication processes must not require cognitive function tests (such as remembering a password, solving a CAPTCHA puzzle, or performing mental arithmetic) as the sole method of login, unless the test allows pasting (so password managers work), provides an alternative method, or uses object or personal content recognition. This criterion directly addresses a major barrier for users with cognitive and memory disabilities. Practical compliance means supporting password managers, offering passkey/biometric login options, or providing email-based magic links.
Accessible Authentication (Enhanced)
Level AAAA stricter version of 3.3.8. Authentication must not rely on any cognitive function test at all, including object recognition and personal content identification. Only fully cognitive-free methods like biometrics, password managers with paste support, and passkeys meet this criterion.
Which Laws Point to Which WCAG Version
Different laws name different versions of WCAG, and some name none at all. Here is where the main ones stand.
| Law | Who it covers | WCAG version |
|---|---|---|
| ADA Title III | Businesses open to the public | No regulation names a standard. The DOJ's 2022 web guidance (opens in new tab) says businesses have flexibility in how they comply and that WCAG provides “helpful guidance.” |
| ADA Title II | State and local governments | WCAG 2.1 Level AA. Under the April 2026 interim final rule (opens in new tab), compliance dates are April 26, 2027 for governments serving 50,000 or more people and April 26, 2028 for smaller governments and special districts. |
| Section 508 | Federal agencies and the technology they buy | The Revised 508 Standards (opens in new tab) incorporate WCAG 2.0 Level AA. |
| European Accessibility Act | Covered products and services sold in the EU | EN 301 549 V4.1.1 aligns its web requirements with WCAG 2.2. Once it is cited in the EU's Official Journal, conforming to it gives a presumption of conformity with the EAA. See our EAA requirements guide. |
WCAG 2.2 Level AA includes the success criteria of 2.1 AA and 2.0 AA (apart from the retired 4.1.1), so it is the safest single target for a website.
Want to know where your site stands?
Run a free scan →Why WCAG 2.2 Matters for Your Business
Even though no regulation currently mandates WCAG 2.2 specifically (the DOJ's Title II rule (opens in new tab) references WCAG 2.1), targeting WCAG 2.2 is the right approach for several reasons:
- Future-proofing: Regulatory standards tend to adopt the latest version of WCAG over time. Organizations that target 2.2 now will not need to scramble when regulations update.
- Backward compatibility: Meeting WCAG 2.2 automatically means you meet 2.1 and 2.0. There is no downside to targeting the latest version.
- Real user impact: The nine new criteria address genuine usability barriers that affect millions of people. Cognitive accessibility and mobile usability are areas where earlier WCAG versions fell short.
- Lawsuit defense: A documented WCAG 2.2 AA effort is the clearest record you can show if a demand letter arrives. No standard makes a site lawsuit-proof, as the ADA website lawsuit statistics show.
- Market reach: An estimated 1.3 billion people worldwide have a disability. Accessible websites serve a broader audience, which is also good for business.
How to Check Your Website Against WCAG 2.2
Evaluating your website against WCAG 2.2 requires a combination of automated testing and manual evaluation. Automated tools like CompliaScan's WCAG checker can detect many issues, particularly target size problems, contrast failures, and missing ARIA attributes. Manual testing is needed for criteria like Consistent Help and Redundant Entry that require understanding the user experience across multiple pages.
A practical testing pass has four parts:
- Automated scan: run a scanner across your key pages to catch contrast, missing alt text, missing labels, and other machine-detectable failures.
- Keyboard pass: put the mouse away and Tab through each page, checking focus order, visible focus, keyboard traps, and whether sticky headers hide the focused element.
- Screen reader pass: listen to your main pages with NVDA or VoiceOver to hear how headings, links, forms, and error messages are announced.
- Ongoing monitoring: rescan on a schedule, because code changes, content updates, and third-party widgets can all add new barriers.
For a detailed walkthrough of each step, read our guide on how to check website accessibility. For a complete criterion-by-criterion checklist, use our interactive WCAG checklist.
Check your compliance status, free
Run a free WCAG 2.2 scan and see exactly which requirements your site meets and which it misses. No signup required, results in under 30 seconds.
Free scan · No signup required · Results in ~30 seconds
Keep reading
All articles →WCAG vs ADA: What's the Difference and Which Applies to You?
WCAG and ADA are related but different. Understand the key differences between WCAG technical standards and ADA legal requirements for your website.
European Accessibility Act Requirements for Websites
What the EAA requires for websites since June 28, 2025, who must comply, and how EN 301 549 V4.1.1 now aligns with WCAG 2.2 AA.
How Much Does a Website Accessibility Audit Cost in 2026?
Accessibility audit pricing breakdown: manual audits ($3,000–$30,000), VPATs, automated tools, and ongoing monitoring. What's actually required vs what's oversold.
Related Resources
Accessibility Compliance Hub
How ADA, WCAG 2.2, Section 508, and the European Accessibility Act apply, broken down by industry.
Compare Accessibility Tools
See how CompliaScan compares to other accessibility scanners and overlay widgets, side by side.
Free Accessibility Tools
Color contrast checker, WCAG 2.2 checklist, alt text checker, and accessibility statement generator.