Skip to main content
The foundation standard

What is WCAG 2.2?

The Web Content Accessibility Guidelines are the technical standard that almost every national accessibility law points to. Know these and you understand what the law actually requires.

The Web Content Accessibility Guidelines (WCAG) are published by the World Wide Web Consortium (W3C) through the Web Accessibility Initiative. Version 2.2 became a W3C Recommendation on 5 October 2023, superseding WCAG 2.1 (2018) and WCAG 2.0 (2008). All three versions are backward-compatible: everything that conformed to 2.0 still conforms to 2.2 if you add the newer criteria.

WCAG 2.2 defines 87 success criteria — testable statements like “all non-text content has a text alternative” or “colour is not the only way to convey information.” Each criterion is assigned a conformance level (A, AA or AAA) based on how fundamental it is to access for people with disabilities.

WCAG is content-type agnostic: the same criteria apply to websites, web apps, PDFs (through PDF/UA), native mobile apps and software interfaces (through EN 301 549 and Section 508). Adoption is near-universal — from the ADA in the United States to the EAA in Europe, the DDA in Australia, the ACA in Canada and the Equality Act in the UK.

Structure

The four POUR principles

Every one of the 87 success criteria sits under one of four principles. If your content fails any principle, people with disabilities cannot use it.

Perceivable

Information and UI components must be presentable in ways users can perceive — it can’t be invisible to every one of their senses.

  • Text alternatives for non-text content (1.1)
  • Captions and alternatives for time-based media (1.2)
  • Content adaptable without losing information (1.3)
  • Sufficient colour contrast and text resizing (1.4)

Operable

UI components and navigation must be operable — users must be able to use the interface with whatever input device they have.

  • Keyboard accessible (2.1)
  • Enough time to read and use content (2.2)
  • No content that causes seizures (2.3)
  • Navigable with clear structure and focus (2.4)
  • Input modalities beyond keyboard (2.5)

Understandable

Information and operation must be understandable — content and behaviour can’t be beyond users’ comprehension.

  • Text is readable (3.1)
  • Content appears and operates predictably (3.2)
  • Users get input assistance (3.3)

Robust

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.

  • Compatible with current and future tools (4.1)
  • Valid, parseable markup (4.1.1 — obsoleted in 2.2)
  • Name, Role, Value for every component (4.1.2)
  • Accessible status messages (4.1.3)
Conformance levels

A, AA, AAA — and which one the law requires

AA is the level almost every law points to. A is the floor below which content is unusable for many people. AAA is the aspirational ceiling.

Level A

30 criteria · minimum

The lowest level. If you fail Level A, some people with disabilities cannot access your content at all. Covers basics like text alternatives, keyboard access, no seizure triggers and language of page. Required by every single accessibility law.

Level AA

28 additional criteria · legal target

The conformance target of virtually every national law: ADA, EAA, EN 301 549, Section 508, DDA, ACA, AODA, Equality Act. Adds contrast ratios, resizable text, captions, consistent navigation and input error prevention. This is the level you should audit to.

Level AAA

29 additional criteria · aspirational

The highest level. W3C specifically notes that full AAA conformance is not required for all content and may be impossible for some content types. Useful for critical services (healthcare, finance, government) but not mandated by law.

What’s new in 2.2

Nine new success criteria — mostly mobile and cognitive

WCAG 2.2 added criteria for touch targets, drag-only interactions, visible focus, redundant entry and cognitive load. Parse (4.1.1) was obsoleted — browsers now handle it reliably.

2.4.11

Focus Not Obscured (Minimum)

When a component gets keyboard focus it must not be entirely hidden by author-created content like sticky headers or cookie banners.

AA
2.4.12

Focus Not Obscured (Enhanced)

Stricter version: no part of the focused component may be hidden by author-created overlays.

AAA
2.4.13

Focus Appearance

Focus indicators must have enough contrast against both the focused element and the background, with a minimum outline area.

AAA
2.5.7

Dragging Movements

All drag-and-drop functionality must have a single-pointer alternative (click or tap). Critical for users with motor impairments.

AA
2.5.8

Target Size (Minimum)

Clickable targets must be at least 24×24 CSS pixels, with exceptions for inline, user-agent and essential targets.

AA
3.2.6

Consistent Help

If help mechanisms (contact info, FAQ, chat) appear on multiple pages, they must appear in the same relative order.

A
3.3.7

Redundant Entry

Information previously entered in the same session must be auto-populated or available — don’t make users retype their address.

A
3.3.8

Accessible Authentication (Minimum)

No cognitive function test (puzzles, memorising strings) required to log in, unless there’s an alternative or object recognition/personal content.

AA
3.3.9

Accessible Authentication (Enhanced)

Stricter version: no cognitive function test even with object-recognition alternatives. Password managers and biometrics are the path forward.

AAA
Legal adoption

Which WCAG version every law points to

Jurisdictions update at different speeds. 2.2 is now the target in the UK and Australia; the US and EU still reference 2.1; Section 508 still references 2.0. All are backward-compatible.

Region
Law / standard
WCAG version
US
ADA Title II final rule (state/local gov)
2.1 AA
US
Section 508 Refresh
2.0 AA
EU
European Accessibility Act / EN 301 549
2.1 AA
UK
Public Sector Bodies Accessibility Regs (PSBAR)
2.2 AA
AU
Digital Service Standard
2.2 AA
CA
Accessible Canada Act / AODA
2.1 AA / 2.0 AA
NZ
NZ Government Web Accessibility Standard
2.2 AA
Next step

See which WCAG 2.2 criteria your site breaks

Our Web Accessibility Checker tests against 77 WCAG 2.2 A and AA criteria in real time and gives you the specific fix for each failure.