Web Content Accessibility Guidelines (WCAG) 2.2

What is WCAG 2.2?

Web Content Accessibility Guidelines (WCAG) 2.2 is a globally recognized technical standard published by the World Wide Web Consortium (W3C) on October 5, 2023 (with a minor editorial update on December 12, 2024 that did not change any success criteria), specifying how to make digital content accessible to people with a wide range of disabilities, including visual, auditory, physical, cognitive, and neurological impairments. Building on WCAG 2.1, it adds nine new success criteria - with a focus on users with cognitive disabilities, low vision, and limited mobility - while removing one obsolete criterion (4.1.1 Parsing) and remaining fully backward compatible. In October 2025, WCAG 2.2 was formally adopted as the international standard ISO/IEC 40500:2025, reinforcing its status as the definitive global benchmark for web accessibility. The standard is organized around four principles - content must be Perceivable, Operable, Understandable, and Robust (POUR) - and offers 87 testable success criteria at Levels A, AA, and AAA.

Who must comply?

WCAG 2.2 is a voluntary technical standard, but it is incorporated by reference into laws and regulations worldwide, making it effectively mandatory for broad categories of organizations. In the United States, the DOJ's ADA Title II final rule requires state and local governments to meet WCAG 2.1 Level AA (with WCAG 2.2 representing current best practice), while Section 508 of the Rehabilitation Act mandates WCAG 2.0 Level AA for federal agencies and their contractors and vendors. In the European Union, the European Accessibility Act (EAA), enforceable from June 28, 2025, and EN 301 549 reference WCAG 2.1 AA - and WCAG 2.2 is increasingly cited as the expected standard by regulators and courts. Private-sector businesses of all sizes face growing litigation risk under the ADA and comparable laws globally if their websites do not meet WCAG 2.2 Level AA.

Key requirements

• Focus Not Obscured: When a user interface component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers or cookie banners (SC 2.4.11, Level AA).
• Focus Appearance: Keyboard focus indicators must meet minimum size and contrast requirements so they are clearly visible to users with low vision (SC 2.4.13, Level AAA; SC 2.4.11 at AA).
• Dragging Movements: Any functionality that relies on a dragging gesture (e.g., sliders, drag-and-drop) must also be operable with a single pointer without dragging, unless dragging is essential (SC 2.5.7, Level AA).
• Target Size (Minimum): Interactive targets such as buttons and links must be at least 24x24 CSS pixels, or adequate spacing must exist between smaller targets to prevent accidental activation (SC 2.5.8, Level AA).
• Consistent Help: If a web page provides a help mechanism - such as a phone number, chat, or contact link - it must appear in the same relative location across pages (SC 3.2.6, Level A).
• Redundant Entry: Information users have previously entered in a process must not be requested again in the same session, unless re-entry is essential or required for security (SC 3.3.7, Level A).
• Accessible Authentication: Authentication processes must not require users to solve a cognitive function test, such as a CAPTCHA, unless an alternative is provided or the test involves object recognition and not memorization (SC 3.3.8, Level AA).

Key dates & deadlines

• October 5, 2023WCAG 2.2 published as a W3C Recommendation - the definitive effective date of the standard globally.
• June 28, 2025European Accessibility Act (EAA) enforcement begins in EU member states; EN 301 549 (which references WCAG 2.1 AA, with 2.2 as best practice) becomes mandatory for covered digital products and services.
• April 26, 2027Extended DOJ Title II ADA compliance deadline for U.S. state and local governments serving a population of 50,000 or more (WCAG 2.1 AA required; extended from the original April 24, 2026 deadline by an April 2026 Interim Final Rule).
• April 26, 2028Extended DOJ Title II ADA compliance deadline for U.S. state and local governments serving fewer than 50,000 people and for special district governments (WCAG 2.1 AA required).

Penalties & enforcement

WCAG 2.2 itself carries no direct penalties - enforcement flows through the laws that incorporate it. In the United States, ADA non-compliance can result in federal civil rights lawsuits, DOJ investigations, consent decrees, and damages; federal web accessibility lawsuits number in the thousands annually (approximately 2,452 federal filings were recorded in 2024, according to ADA Title III tracking data), with courts increasingly citing WCAG 2.2 as the de facto standard. In the European Union, the EAA empowers national regulators to impose country-specific fines for non-compliant digital products and services; penalty structures vary by member state - Germany's maximum is €100,000 per violation, Italy's ranges from €30,000 to €1,000,000 depending on severity, and Spain also reaches €1,000,000 for the most serious violations - plus potential market withdrawal orders. Organizations procuring ICT for the U.S. federal government that violate Section 508 face contract disputes, agency complaints to the U.S. Access Board, and reputational harm.

How WCAG 2.2 relates to WCAG

WCAG 2.2 is the standard itself - the current version of the Web Content Accessibility Guidelines, superseding WCAG 2.1 (published 2018) and WCAG 2.0 (published 2008). It is fully backward compatible: a site conforming to WCAG 2.2 Level AA also satisfies WCAG 2.1 and 2.0 at the same level. Many regulations still formally reference WCAG 2.1 or 2.0 (e.g., ADA Title II final rule at WCAG 2.1 AA; Section 508 at WCAG 2.0 AA), but WCAG 2.2 Level AA is widely treated by legal counsel, courts, and accessibility professionals as the current minimum best practice for defensible compliance.

How EqualWeb helps you meet WCAG 2.2

EqualWeb's AI Accessibility Widget can be deployed with a single line of code and automatically remediates approximately 80% of common WCAG 2.2 issues in real time on the client side - including focus management, color contrast adjustments, and accessible interaction profiles - helping organizations make measurable progress toward Level AA conformance. The widget alone does not make a site fully conformant; issues requiring code-level or structural remediation (such as full Accessible Authentication or Focus Appearance compliance) need expert intervention. For those remaining issues, EqualWeb's Managed Compliance service pairs clients with IAAP/CPWA-certified experts who audit, remediate, monitor, and certify toward full WCAG 2.2 Level AA conformance, delivering a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a supporting evidence pack. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score with regression alerts, so organizations can track conformance against WCAG 2.2 success criteria over time and catch regressions before they create legal exposure. The Accessibility Testing suite - including an automated checker, site crawler, and ongoing monitor - maps findings directly to WCAG 2.2 success criteria, giving development and compliance teams actionable remediation priorities. For organizations with PDF-heavy workflows, EqualWeb's PDF Tools check and remediate documents against PDF/UA and Section 508 standards, addressing a category of content that WCAG 2.2 explicitly extends to through WCAG2ICT guidance.

WCAG 2.2 - frequently asked questions

Official sources & further reading

• Web Content Accessibility Guidelines (WCAG) 2.2 - W3C Recommendation
• What's New in WCAG 2.2 - W3C WAI
• WCAG 2.2 Approved as ISO/IEC 40500:2025 - W3C WAI Announcement

Related standards & laws