2.4.11
AAFocus Not Obscured (Minimum)
When an element receives keyboard focus, it must not be completely hidden behind sticky headers, cookie banners, or chat overlays.
WCAG 2.2 quick reference
The plain-English WCAG 2.2 checklist
Every Level A and AA success criterion in one quick reference — what changed from WCAG 2.1, the 9 new criteria in 2.2, and how to test your site against them for free.
Working toward US compliance? Read our guide on how to make your website ADA compliant — courts use WCAG as the measuring stick.
- All A + AA criteria
- 9 new 2.2 criteria explained
- Free WCAG scan
Launcher ready
your-website.com
Page preview
Visitor-adjustable experience
The embed does not change your stack — it adds the same panel customers configure in the dashboard.
Launcher ready
Default grey button — same as the live Inclusense widget.
Oct 2023
WCAG 2.2 became a W3C standard
9
New success criteria added
Level AA
The target laws point to
The basics
What is WCAG 2.2?
The current version of the standard behind virtually every accessibility law — published by the W3C in October 2023.
The Web Content Accessibility Guidelines (WCAG) define, in testable terms, what it means for a website to work for people with visual, motor, auditory, and cognitive disabilities. Criteria are organised under four principles — Perceivable, Operable, Understandable, Robust — and graded at three levels: A (minimum), AA (the legal benchmark), and AAA (enhanced).
WCAG 2.2 is backwards compatible: it keeps every requirement from WCAG 2.1 except the obsolete 4.1.1 Parsing criterion, and adds nine new ones. That means a site meeting WCAG 2.2 AA automatically meets 2.1 AA — the version US courts, the DOJ, and the European Accessibility Act currently reference — so building to this checklist covers both.
Before working through the list, get a baseline: run our free WCAG accessibility scanner to see which criteria your pages already fail — no login required.
New in 2.2
The 9 new success criteria in WCAG 2.2
Six are Level A or AA — these are the ones that affect your compliance target. Three are AAA.
2.5.7
AADragging Movements
Any action that relies on dragging — sliders, sortable lists, map panning — needs a simple single-pointer alternative like buttons or taps.
2.5.8
AATarget Size (Minimum)
Clickable targets must be at least 24×24 CSS pixels, or have enough spacing around them so users don't hit the wrong control.
3.2.6
AConsistent Help
If you offer help — contact details, live chat, FAQs — it must appear in the same relative place on every page that includes it.
3.3.7
ARedundant Entry
Don't make users re-type information they already entered in the same process — auto-populate it or make it selectable.
3.3.8
AAAccessible Authentication (Minimum)
Logins can't depend on cognitive tests like memorising codes or solving puzzles — allow paste, password managers, or alternatives.
2.4.12
AAAFocus Not Obscured (Enhanced)
The stricter version: no part of the focused element may be hidden by other content — the whole component stays visible.
2.4.13
AAAFocus Appearance
Focus indicators must be clearly visible: at least as large as a 2px perimeter outline with 3:1 contrast against the unfocused state.
3.3.9
AAAAccessible Authentication (Enhanced)
The stricter version: no cognitive tests at all in login flows — not even object-recognition or image CAPTCHAs.
One criterion was removed: 4.1.1 Parsing is obsolete in WCAG 2.2 because modern browsers and assistive technologies handle imperfect HTML consistently.
Quick reference
WCAG 2.2 AA checklist, principle by principle
The Level A and AA criteria condensed into plain-English checks — success criterion numbers in brackets so you can look up the full text.
Perceivable
Users must be able to perceive your content — see it, hear it, or read it through assistive technology.
- Every meaningful image has descriptive alt text; decorative images are hidden from screen readers (1.1.1)
- Pre-recorded video has captions, and audio content has transcripts (1.2.1–1.2.5)
- Structure uses real markup — headings, lists, tables, and form labels, not styled text (1.3.1)
- Form fields that collect user data identify their purpose so autofill works (1.3.5)
- Text contrast is at least 4.5:1 — 3:1 for large text (1.4.3)
- Text can be resized to 200% without losing content or function (1.4.4)
- Content reflows on small screens without two-directional scrolling (1.4.10)
- Buttons, form borders, icons, and charts have 3:1 contrast (1.4.11)
- Layouts survive user-adjusted text spacing without clipping (1.4.12)
- Tooltips and hover content can be dismissed and hovered without disappearing (1.4.13)
Operable
Users must be able to operate every control — with a keyboard alone, a touch screen, or assistive technology.
- Everything works with a keyboard, and focus is never trapped (2.1.1, 2.1.2)
- Time limits can be extended; auto-moving content can be paused (2.2.1, 2.2.2)
- Nothing flashes more than three times per second (2.3.1)
- Pages have a skip link, descriptive titles, logical focus order, and clear link text (2.4.1–2.4.4)
- Headings and labels are descriptive, and keyboard focus is clearly visible (2.4.6, 2.4.7)
- Focused elements aren't hidden behind sticky headers or overlays (2.4.11 — new in 2.2)
- Complex gestures and dragging have single-pointer alternatives (2.5.1, 2.5.7 — new in 2.2)
- Clickable targets are at least 24×24 CSS pixels or well spaced (2.5.8 — new in 2.2)
Understandable
Users must be able to understand your content and predict how the interface behaves.
- The page language — and any language changes — are set in code (3.1.1, 3.1.2)
- Nothing changes context unexpectedly when an element gets focus or input (3.2.1, 3.2.2)
- Navigation and repeated components stay consistent across pages (3.2.3, 3.2.4)
- Help options appear in the same place on every page (3.2.6 — new in 2.2)
- Form errors are identified in text, explained, and easy to correct (3.3.1, 3.3.3)
- Every input has a visible label and clear instructions (3.3.2)
- Legal and financial submissions can be reviewed and reversed (3.3.4)
- Users never re-enter information they already provided in the same flow (3.3.7 — new in 2.2)
- Logins work without puzzles or memorisation — paste and password managers allowed (3.3.8 — new in 2.2)
Robust
Your code must work reliably with browsers and assistive technologies — today and as they evolve.
- Custom controls expose an accessible name, role, and value through correct ARIA (4.1.2)
- Status messages — form saved, items in cart, errors — are announced to screen readers without moving focus (4.1.3)
- Note: 4.1.1 Parsing was removed in WCAG 2.2 — modern browsers handle malformed HTML consistently, so it always passes
This condenses the criteria most audits flag — for the normative wording, see the official W3C quick reference. To find which of these your site fails right now, run a free accessibility check.
Full reference table
WCAG 2.2 success criteria quick reference (Level A & AA)
Every Level A and AA success criterion in WCAG 2.2 — number, name, level, and a one-line plain-English requirement. Criteria marked New were added in WCAG 2.2.
1. Perceivable
| SC | Success criterion | Level | What it requires |
|---|---|---|---|
| 1.1.1 | Non-text Content | A | Provide text alternatives (alt text) for images and non-text content. |
| 1.2.1 | Audio-only & Video-only (Prerecorded) | A | Give a transcript for audio, and a description or transcript for silent video. |
| 1.2.2 | Captions (Prerecorded) | A | Add captions to all prerecorded video with audio. |
| 1.2.3 | Audio Description or Media Alternative | A | Provide audio description or a full text alternative for prerecorded video. |
| 1.2.4 | Captions (Live) | AA | Add real-time captions to live audio content. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Provide audio description for all prerecorded video. |
| 1.3.1 | Info and Relationships | A | Convey structure with real markup — headings, lists, tables, labels. |
| 1.3.2 | Meaningful Sequence | A | Ensure reading and navigation order in the DOM makes sense. |
| 1.3.3 | Sensory Characteristics | A | Don't rely on shape, size, or position alone (e.g. "the button on the right"). |
| 1.3.4 | Orientation | AA | Don't lock content to portrait or landscape unless essential. |
| 1.3.5 | Identify Input Purpose | AA | Mark up common form fields so browsers can autofill them. |
| 1.4.1 | Use of Color | A | Don't use color as the only way to convey information. |
| 1.4.2 | Audio Control | A | Let users pause or stop audio that plays for more than 3 seconds. |
| 1.4.3 | Contrast (Minimum) | AA | Text contrast at least 4.5:1 (3:1 for large text). |
| 1.4.4 | Resize Text | AA | Text resizes to 200% without loss of content or function. |
| 1.4.5 | Images of Text | AA | Use real text instead of images of text where possible. |
| 1.4.10 | Reflow | AA | Content reflows to a single column at 320px with no horizontal scroll. |
| 1.4.11 | Non-text Contrast | AA | UI components and graphics have at least 3:1 contrast. |
| 1.4.12 | Text Spacing | AA | No loss of content when users adjust line, letter, and word spacing. |
| 1.4.13 | Content on Hover or Focus | AA | Hover/focus popups are dismissable, hoverable, and persistent. |
2. Operable
| SC | Success criterion | Level | What it requires |
|---|---|---|---|
| 2.1.1 | Keyboard | A | All functionality works with a keyboard alone. |
| 2.1.2 | No Keyboard Trap | A | Keyboard focus can always move away from any component. |
| 2.1.4 | Character Key Shortcuts | A | Single-key shortcuts can be turned off or remapped. |
| 2.2.1 | Timing Adjustable | A | Users can turn off, adjust, or extend time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Provide controls for moving, blinking, or auto-updating content. |
| 2.3.1 | Three Flashes or Below Threshold | A | Nothing flashes more than three times per second. |
| 2.4.1 | Bypass Blocks | A | Offer a skip link or landmarks to bypass repeated content. |
| 2.4.2 | Page Titled | A | Every page has a descriptive, unique title. |
| 2.4.3 | Focus Order | A | Focus moves in a logical, meaningful order. |
| 2.4.4 | Link Purpose (In Context) | A | Link purpose is clear from its text or context. |
| 2.4.5 | Multiple Ways | AA | Provide more than one way to find pages (search, menu, sitemap). |
| 2.4.6 | Headings and Labels | AA | Headings and labels describe topic or purpose. |
| 2.4.7 | Focus Visible | AA | Keyboard focus is always clearly visible. |
| 2.4.11 | Focus Not Obscured (Minimum)New | AA | Focused elements aren't fully hidden by sticky headers or overlays. |
| 2.5.1 | Pointer Gestures | A | Multipoint or path gestures have a single-pointer alternative. |
| 2.5.2 | Pointer Cancellation | A | Actions complete on release, so users can abort by moving away. |
| 2.5.3 | Label in Name | A | A control's visible label is part of its accessible name. |
| 2.5.4 | Motion Actuation | A | Device-motion functions have a UI alternative and can be disabled. |
| 2.5.7 | Dragging MovementsNew | AA | Dragging actions have a simple single-pointer alternative. |
| 2.5.8 | Target Size (Minimum)New | AA | Clickable targets are at least 24×24 CSS pixels or well-spaced. |
3. Understandable
| SC | Success criterion | Level | What it requires |
|---|---|---|---|
| 3.1.1 | Language of Page | A | The page's default language is set in code. |
| 3.1.2 | Language of Parts | AA | Language changes within content are marked up. |
| 3.2.1 | On Focus | A | Receiving focus doesn't trigger an unexpected change of context. |
| 3.2.2 | On Input | A | Changing a setting doesn't auto-trigger a surprising context change. |
| 3.2.3 | Consistent Navigation | AA | Navigation appears in the same order across pages. |
| 3.2.4 | Consistent Identification | AA | The same components are labelled consistently everywhere. |
| 3.2.6 | Consistent HelpNew | A | Help options appear in the same relative place on each page. |
| 3.3.1 | Error Identification | A | Input errors are identified and described in text. |
| 3.3.2 | Labels or Instructions | A | Form fields have labels or instructions. |
| 3.3.3 | Error Suggestion | AA | Suggest a correction when an input error is detected. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Let users review, correct, or reverse important submissions. |
| 3.3.7 | Redundant EntryNew | A | Don't make users re-enter info already given in the same process. |
| 3.3.8 | Accessible Authentication (Minimum)New | AA | Logins don't depend on memory tests or puzzles; allow paste. |
4. Robust
| SC | Success criterion | Level | What it requires |
|---|---|---|---|
| 4.1.2 | Name, Role, Value | A | Custom UI exposes correct name, role, and value to assistive tech. |
| 4.1.3 | Status Messages | AA | Status updates are announced to screen readers without focus change. |
That's all 55 Level A and AA success criteria in WCAG 2.2. For the full normative wording, see the official W3C quick reference, or scan your site against them with a WCAG accessibility scanner.
Conformance levels
WCAG levels A, AA, and AAA explained
Each criterion carries a level — your conformance level is the highest one you fully meet.
Level A
The minimum
The most basic barriers — keyboard access, alt text, no keyboard traps. Failing Level A means some users are locked out entirely. 31 criteria in WCAG 2.2 sit at this level.
Level AA
The legal benchmark
What laws and courts actually require — the ADA (via DOJ guidance), Section 508, the European Accessibility Act, and public procurement rules all point to Level AA. This is the target for almost every website.
Level AAA
The gold standard
Enhanced criteria like sign language for video and 7:1 contrast. Valuable where you can apply them, but not required by law — W3C itself says AAA isn't achievable for all content.
WCAG 2.1 vs 2.2 — which should you follow?
Follow 2.2. Because it contains everything in 2.1 AA (minus the obsolete parsing rule), meeting WCAG 2.2 AA automatically satisfies the 2.1 AA benchmark that the ADA, Section 508, and the European Accessibility Act currently reference. If you already meet 2.1 AA, the gap is just six new A/AA criteria: focus visibility, dragging alternatives, target size, consistent help, redundant entry, and accessible logins. See the full comparison in WCAG 2.1 vs 2.2: what actually changed.
Turning the checklist into compliance
Structural criteria — alt text, labels, contrast, ARIA — get fixed in your code, guided by WCAG scan results. Alongside those fixes, the Inclusense accessibility widget gives every visitor working controls today — contrast, text size, reading support, reduced motion — with a free 14-day trial, no credit card required. For the US legal angle, see our ADA compliance guide; for Europe, the EAA compliance widget.
Test it
Check your site against WCAG 2.2 in minutes
Automated scanning covers the criteria machines can measure — contrast, alt text, labels, ARIA, structure — and flags each finding with WCAG-oriented tags and severity. Run one free guest scan on up to 5 pages, no login required, then verify the rest manually: keyboard-only navigation, focus visibility, and a screen reader pass on your key flows.
Run a free WCAG scanFAQ
WCAG 2.2 checklist FAQ
What is WCAG 2.2?
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, published as a W3C standard in October 2023. It defines testable success criteria for making websites usable by people with visual, motor, auditory, and cognitive disabilities, organised under four principles: Perceivable, Operable, Understandable, and Robust. It builds on WCAG 2.1 by adding 9 new success criteria and removing one (4.1.1 Parsing).
What's new in WCAG 2.2?
WCAG 2.2 adds 9 success criteria: Focus Not Obscured (2.4.11 AA, 2.4.12 AAA), Focus Appearance (2.4.13 AAA), Dragging Movements (2.5.7 AA), Target Size Minimum (2.5.8 AA), Consistent Help (3.2.6 A), Redundant Entry (3.3.7 A), and Accessible Authentication (3.3.8 AA, 3.3.9 AAA). It also removes 4.1.1 Parsing, which modern browsers made obsolete.
Is WCAG 2.2 required by law?
Laws typically reference a specific WCAG version: US courts and the DOJ currently point to WCAG 2.1 Level AA for the ADA, and the European Accessibility Act relies on EN 301 549, which is also based on WCAG 2.1. But WCAG 2.2 is backwards compatible — a site that meets WCAG 2.2 AA automatically meets 2.1 AA — so building to 2.2 satisfies today's legal benchmarks and prepares you for updates.
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 keeps every requirement from 2.1 except 4.1.1 Parsing (removed as obsolete) and adds 9 new criteria focused on keyboard focus visibility, touch target size, dragging alternatives, consistent help placement, and accessible logins. If you already meet WCAG 2.1 AA, closing the gap to 2.2 AA usually means checking six new A/AA criteria.
How many success criteria are in WCAG 2.2?
WCAG 2.2 has 86 success criteria in total: 31 at Level A, 24 at Level AA, and 31 at Level AAA. For practical compliance, the 55 criteria at Levels A and AA are what matter — that's the conformance target laws, courts, and procurement rules use.
What WCAG level should my website meet?
Level AA. It's the benchmark used by the ADA (per DOJ guidance), Section 508, the European Accessibility Act, and most procurement requirements worldwide. Level A alone leaves serious barriers in place, and Level AAA is aspirational — W3C itself notes that AAA can't be applied to all content.
How do I test my website against WCAG 2.2?
Start with an automated scan — it catches contrast failures, missing alt text, unlabeled forms, and ARIA problems in minutes, and Inclusense's scanner maps findings to WCAG-oriented rules including 2.2 patterns. Then test manually what automation can't judge: navigate key pages with only a keyboard, check focus visibility, and try your forms with a screen reader.
Can an accessibility widget make my website WCAG 2.2 compliant?
Not on its own — no tool can, and widgets that promise instant compliance overstate what overlays do. A widget gives visitors immediate working controls (contrast, text size, reading support, reduced motion) while structural issues like missing alt text and unlabeled forms get fixed in code. The strongest position combines a widget with scan-driven remediation.
Try Inclusense, Risk-Free!
We're confident you'll love Inclusense! Try it with zero risk — if it's not the right fit, you're covered by our money-back guarantee. No commitments, no hassle.