---
title: "WCAG 2.2 explained: web accessibility guidelines | Quantlix"
description: "WCAG 2.2 is the W3C standard for accessible web content. Learn what changed from WCAG 2.1, how conformance levels work and how to build it into your software."
canonical: "https://quantlix.com/en/standards/wcag-2-2/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/wcag-2-2/
Language: en
Description: WCAG 2.2 is the W3C standard for accessible web content. Learn what changed from WCAG 2.1, how conformance levels work and how to build it into your software.

**WCAG 2.2** [Accessibility](https://quantlix.com/en/standards/#accessibility)

# WCAG 2.2: the guidelines for accessible web content

WCAG 2.2 is the W3C Recommendation that sets testable success criteria for making websites, web apps and digital content usable by people with disabilities, at conformance levels A, AA and AAA.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/wcag-2-2/#standard-overview)

## At a glance

**Full name**

Web Content Accessibility Guidelines (WCAG) 2.2

**Published by**

World Wide Web Consortium (W3C), Accessibility Guidelines Working Group, part of the Web Accessibility Initiative (WAI)

**Type**

W3C Recommendation (web standard), also published as ISO/IEC 40500:2025

**Current version**

W3C Recommendation of 5 October 2023, updated 12 December 2024; WCAG 3.0 is a Working Draft (10 September 2026) and does not replace it

**Applies to**

Web pages and web apps, and through the laws and standards that adopt it, mobile apps, software and electronic documents

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- WCAG 2.2 adds nine success criteria to WCAG 2.1, covering focus visibility, target size, dragging, consistent help and authentication.
- It removes 4.1.1 Parsing, and content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0.
- Laws and procurement rules usually point to Level AA, which means meeting every Level A and Level AA success criterion.
- ISO/IEC 40500:2025 is identical to the October 2023 version, while WCAG 3 is still an early draft.

### What is WCAG 2.2?

WCAG 2.2 is **the W3C standard that defines how to make web content accessible to people with disabilities**. It was published as a W3C Recommendation on 5 October 2023 and updated on 12 December 2024. The October 2023 text is also an international standard, ISO/IEC 40500:2025.

It exists so that accessibility can be tested rather than argued about. Instead of general advice, WCAG gives specific success criteria, such as minimum text contrast or keyboard access to every function. That makes accessibility something a designer can plan, a developer can build and a tester can check, and it helps people who use screen readers, magnification, voice control, switches or simply a phone in bright sunlight.

### What WCAG 2.2 covers

- **Four principles.** Content must be Perceivable, Operable, Understandable and Robust, the last meaning browsers and assistive technologies can interpret it reliably.
- **Guidelines.** Thirteen guidelines under those principles, such as text alternatives, keyboard accessibility, readable text and predictable behavior.
- **Success criteria.** Testable statements under each guideline, each assigned a level: A, AA or AAA.
- **Conformance requirements.** Rules for what a claim means, such as covering full pages and every page in a complete process like a checkout.
- **Supporting documents.** Understanding notes and techniques that explain the intent of each criterion and ways to meet it, without being part of the normative text.

### What changed from WCAG 2.1

WCAG 2.2 adds **nine new success criteria**. Three help keyboard users: Focus Not Obscured, in Minimum (AA) and Enhanced (AAA) forms, so sticky headers and banners do not hide the focused element, and Focus Appearance at Level AAA. Dragging Movements asks for a single-pointer alternative to drag and drop, and Target Size (Minimum) sets a 24 by 24 CSS pixel minimum for most click targets, with exceptions.

The other four help people with cognitive and memory disabilities. Consistent Help keeps help options in the same place, Redundant Entry avoids asking for the same information twice in a process, and Accessible Authentication removes memory or puzzle tests from login unless an alternative exists, which in practice means letting password managers and paste work.

The update also removes 4.1.1 Parsing, because modern browsers and assistive technologies no longer depend on it. The W3C notes that content conforming to WCAG 2.2 also conforms to 2.1 and 2.0, which makes 2.2 a sensible target even where a rule names an older version.

### How it shows up in software projects

- **Design system.** Focus styles, color contrast and target sizes are set once as tokens and components, so every screen inherits them.
- **Forms and sign-in.** Login flows allow pasting and password managers, and multi-step forms carry earlier answers forward.
- **Testing.** Automated checks in the build pipeline catch common failures, while manual keyboard and screen reader testing covers what tools cannot judge.
- **Content and media.** Editors get guidance and fields for alternative text, captions and clear headings, so new content stays accessible.
- **Evidence.** Test results, known issues and fixes are recorded per release, which feeds an Accessibility Conformance Report when customers ask for one.

### How we work with WCAG 2.2

We design and build accessible products from the start: accessible component libraries in [UX and UI design](https://quantlix.com/en/services/ux-ui-design/), [web application](https://quantlix.com/en/services/web-application-development/) development with WCAG checks in the pipeline and audits of existing sites with a prioritized fix plan. For public bodies and companies selling into Europe, we map the same work to [EN 301 549](https://quantlix.com/en/standards/en-301-549/), and for U.S. federal buyers to [Section 508](https://quantlix.com/en/standards/section-508/).

A conformance claim belongs to the organization that publishes the content, ideally backed by independent testing. Our part is to build products that meet the criteria and to document the evidence clearly. See where this matters most in [public and social services](https://quantlix.com/en/industries/public-and-social-services/) and [retail and ecommerce](https://quantlix.com/en/industries/retail-and-ecommerce/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Retail & E-commerce](https://quantlix.com/en/industries/retail-and-ecommerce/)

  Connected stores, online commerce and personalized shopping experiences
- ### [Marketing & Advertising](https://quantlix.com/en/industries/marketing-and-advertising/)

  Campaign operations, audience insights and marketing analytics
- ### [Public & Social Services](https://quantlix.com/en/industries/public-and-social-services/)

  Accessible public services, case management and community programs
- ### [Education](https://quantlix.com/en/industries/education/)

  Learning platforms, student services and institutional operations
- ### [Hospitality](https://quantlix.com/en/industries/hospitality/)

  Guest experiences, booking platforms and hospitality operations

## Related standards

[All standards](https://quantlix.com/en/standards/)

- EN 301 549

  ### [European ICT accessibility standard](https://quantlix.com/en/standards/en-301-549/)

  EN 301 549 is the European standard that sets accessibility requirements for ICT products and services, from websites and apps to software, documents, hardware and support services.
- Section 508

  ### [U.S. federal ICT accessibility](https://quantlix.com/en/standards/section-508/)

  Section 508 is the U.S. law that requires federal agencies to make the information and communication technology they develop, buy, maintain or use accessible to people with disabilities.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [UX/UI design](https://quantlix.com/en/services/ux-ui-design/)

Quantlix designs digital experiences through user research, interaction design and visual systems, connecting understandable interfaces to real user tasks.

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

### [Mobile app development](https://quantlix.com/en/services/mobile-app-development/)

Quantlix builds mobile applications for iOS and Android, connecting device capabilities and business services through clear, accessible mobile experiences.

## Questions, answered

What teams usually ask us about this standard.

**Is WCAG 2.2 a legal requirement?**

WCAG is a W3C standard, not a law. Laws and standards make it binding by reference: EN 301 549 V4.1.1 in Europe uses WCAG 2.2 Level AA, while the U.S. Section 508 standards still reference WCAG 2.0 and the ADA Title II rule references WCAG 2.1.

**What is new in WCAG 2.2?**

Nine success criteria: Focus Not Obscured (Minimum and Enhanced), Focus Appearance, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum and Enhanced). Six of them are at Level A or AA.

**Is WCAG 3 replacing WCAG 2.2?**

Not yet. WCAG 3.0 is a W3C Working Draft, last published on 10 September 2026. The W3C says it will not supersede WCAG 2, and that WCAG 2 will not be deprecated for several years after WCAG 3 is finished.

**Which WCAG level should we aim for?**

Level AA is the usual target, because most legal and procurement references use it. The W3C does not recommend requiring Level AAA as a general policy for whole sites, because some content cannot satisfy every AAA criterion.

**Can a website be certified for WCAG 2.2?**

The W3C does not certify websites or products. An organization can make a conformance claim for specific pages, and an independent audit or an Accessibility Conformance Report documents how well each criterion is met.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [WCAG 2.2, W3C Recommendation](https://www.w3.org/TR/WCAG22/)
- [WCAG 2 overview from W3C WAI](https://www.w3.org/WAI/standards-guidelines/wcag/)
- [WCAG 3.0 Working Draft](https://www.w3.org/TR/wcag-3.0/)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
