What is WCAG? 4 Principles Levels A / AA / AAA New in 2.2 Legal requirements Who it protects Quick checklist
Complete guide

Understanding WCAG 2.2

Everything you need to know about the Web Content Accessibility Guidelines — what they are, why they matter legally, and what your website needs to comply.

What is WCAG?

1.3B
people worldwide live with a disability
96%
of home pages have detectable WCAG failures
4,000+
ADA web accessibility lawsuits filed in 2023

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility, published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI). They define how to make web content more accessible to people with disabilities.

WCAG covers a wide range of recommendations for making web content more accessible to people who are blind or have low vision, deaf or hard of hearing, have limited movement, have speech disabilities, have photosensitivity, have learning or cognitive disabilities, or some combination of these.

"Following these guidelines will make content accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these."

— W3C Web Accessibility Initiative

WCAG version history

WCAG has evolved through several versions. WCAG 2.2 (published October 2023) is the current recommended standard and the one WebPossum tests against.

1999WCAG 1.0 — first published guideline
2008WCAG 2.0 — technology-neutral approach introduced
2018WCAG 2.1 — mobile and cognitive additions
2023WCAG 2.2 — current standard ← we test this

The 4 POUR principles

WCAG is built around four core principles, often called POUR. Every success criterion in WCAG falls under one of these four categories.

1

Perceivable

Information and interface components must be presentable to users in ways they can perceive.

Alt text for images
Captions for video
Sufficient color contrast
Text resizable to 200%
2

Operable

User interface components and navigation must be operable by all users.

All functionality via keyboard
No keyboard traps
Skip navigation links
Sufficient time limits
3

Understandable

Information and the operation of the interface must be understandable.

Language declared in HTML
Consistent navigation
Clear error messages
Labels for all inputs
4

Robust

Content must be robust enough to be reliably interpreted by assistive technologies.

Valid, parseable HTML
Correct ARIA roles
Status messages announced
Name, role, value on controls

Conformance levels: A, AA, and AAA

WCAG organizes its success criteria into three levels of conformance. Most organizations and legal frameworks target Level AA as their standard.

Level A — Minimum

Basic accessibility

The most basic requirements. Failing Level A makes content completely inaccessible to some users. This is the floor, not the goal.

30 success criteria · Examples: alt text, no keyboard traps, page title

1.1.1 Non-text content 2.1.1 Keyboard 2.4.2 Page titled 4.1.2 Name role value
Level AAA — Enhanced

The highest standard

Not required by any current law for entire websites. It is not possible to satisfy all AAA criteria for all content.

28 additional criteria · Enhanced contrast, sign language, no timing

1.4.6 Contrast Enhanced (7:1) 2.2.3 No Timing

What is new in WCAG 2.2

WCAG 2.2 (October 2023) added 9 new success criteria compared to WCAG 2.1. These focus primarily on cognitive accessibility, mobile usability, and focus visibility.

Focus Not Obscured (Minimum)

2.4.11 — AA

When a UI component receives keyboard focus, it must not be entirely hidden by sticky headers or overlays.

Focus Not Obscured (Enhanced)

2.4.12 — AAA

No part of the focused element is hidden by author-created content. Stricter version of 2.4.11.

Focus Appearance

2.4.13 — AAA

The keyboard focus indicator must have a minimum area and sufficient contrast ratio of at least 3:1.

Dragging Movements

2.5.7 — AA

All functionality that uses dragging can also be achieved with a single pointer action.

Target Size (Minimum)

2.5.8 — AA

The size of pointer input targets is at least 24×24 CSS pixels. Helps users with motor disabilities.

Consistent Help

3.2.6 — A

Help mechanisms must appear in the same relative order when repeated across multiple pages.

Redundant Entry

3.3.7 — A

Information previously entered must be auto-populated or available for selection in multi-step forms.

Accessible Authentication (Minimum)

3.3.8 — AA

A cognitive function test must not be required in authentication unless an alternative is provided.

Accessible Authentication (Enhanced)

3.3.9 — AAA

No cognitive function test is required in any authentication step. No exceptions.

Who WCAG protects

Accessibility affects a broader range of users than most people assume. WCAG criteria address these disability categories:

Visual

Blindness, low vision, color blindness. Screen readers, magnification, and high-contrast modes must work correctly.

Auditory

Deafness and hard of hearing. Audio content must have captions or transcripts.

Motor

Limited fine motor control, tremors, paralysis. Keyboard navigation and sufficient target sizes are critical.

Cognitive

Dyslexia, ADHD, memory impairments. Clear language, consistent navigation, and error prevention help.

Speech

Users who cannot use voice interfaces must have non-voice alternatives available.

Photosensitive

Photosensitive epilepsy. Content must not flash more than 3 times per second.

Accessibility also benefits users without permanent disabilities: people using a phone in sunlight, people in noisy environments, people with a broken arm, and elderly users.

Quick WCAG 2.2 AA checklist

The most common WCAG 2.2 Level AA failures found on real websites. WebPossum automatically tests all of these.

Must have (automated)

All images have descriptive alt text
Text contrast ratio is at least 4.5:1 (normal) or 3:1 (large text)
All form inputs have associated labels
Page has a descriptive title
HTML lang attribute is set
Heading hierarchy is logical (h1 → h2 → h3)
Links have descriptive text (not "click here")
Page has landmark regions (main, nav, footer)
Keyboard focus is visible at all times
Interactive elements are at least 24×24 CSS px (WCAG 2.2)

Must have (manual testing)

Full site navigable by keyboard only
Videos have synchronized captions
Error messages are descriptive and suggest correction
No authentication requires cognitive test without alternative

Common failures

Images with missing or empty alt text (most common failure)
Gray text on white backgrounds (insufficient contrast)
CSS that removes the focus outline (outline: none)
Icon-only buttons with no accessible name
Missing form labels or placeholder used instead of label
Keyboard traps in modal dialogs

Test your site now — free

WebPossum checks all automated criteria instantly using real axe-core.

Run free audit →