WCAG 2.2 Checklist
A WCAG checklist turns the Web Content Accessibility Guidelines into a list you can work through one success criterion at a time. This one has all 86 WCAG 2.2 success criteria with a plain-English summary of each: 31 at Level A, 24 at Level AA and 31 at Level AAA. Most teams aim for Level AA, which means meeting all 55 Level A and AA criteria.
Tick each criterion your site meets and your progress saves in this browser. The axe-core rules in our scanner cover part of 20 of the 55 Level A and AA criteria (marked Partly automated), so you can test the automatable criteria now with the free WCAG checker and review the rest by hand. See how CompliaScan tests, including the checks we run on top of axe-core.
0 of 55 Level A and AA criteria met (WCAG 2.2)
0%
Level AAA (optional): 0 of 31 met
Partly automated means the free CompliaScan scan runs an axe-core rule mapped to that criterion. A clean scan does not prove the criterion is met, so review it by hand as well. Progress saves in this browser only.
People can perceive the content: text alternatives, captions, structure that survives restyling, and readable contrast.
Guideline 1.1 Text Alternatives
Images, icons, charts and other non-text content have a text alternative that serves the same purpose.
Guideline 1.2 Time-based Media
Prerecorded audio-only content has a transcript, and prerecorded video-only content has a transcript or an audio track.
Prerecorded video with sound has synchronized captions.
- Level AW3C guidance for 1.2.3 Audio Description or Media Alternative (Prerecorded) (opens in new tab)
Prerecorded video has audio description or a full text alternative such as a descriptive transcript.
Live video with sound, such as a webinar or live stream, has real-time captions.
Prerecorded video has audio description of the important visual information.
Prerecorded video with sound includes sign language interpretation.
When natural pauses are too short for audio description, the video pauses to make room for extended description.
Prerecorded video, with or without sound, has a full text alternative such as a descriptive transcript.
Live audio-only content, such as a live radio stream, has a text alternative like live captions or a script.
Guideline 1.3 Adaptable
Structure shown visually, such as headings, lists, tables and form labels, is also defined in the code or stated in text.
When reading order affects meaning, the code order gives a correct reading sequence.
Instructions do not rely only on shape, color, size, visual position, orientation or sound.
Content works in both portrait and landscape unless one orientation is essential.
Fields that collect personal details, such as name, email or address, declare their purpose in code, for example with autocomplete.
The purpose of controls, icons and page regions is defined in code so tools can adapt them for users.
Guideline 1.4 Distinguishable
Color is not the only visual way to convey information, show an action, prompt a response or tell elements apart.
Audio that plays automatically for more than 3 seconds can be paused, stopped or turned down separately from the system volume.
Text has a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text.
Text can be resized to 200 percent without assistive technology and without losing content or functionality.
Real text is used instead of images of text, except for logos and other cases where the exact presentation is essential.
Text has a contrast ratio of at least 7:1 against its background, or 4.5:1 for large text.
Prerecorded speech has no background sound, background sound that can be turned off, or background sound at least 20 dB quieter.
Blocks of text can be shown in user-chosen colors, at most 80 characters wide, not justified, with 1.5 line spacing, and resized to 200 percent without horizontal scrolling.
Images of text are used only for decoration or where that exact presentation is essential, such as a logo.
Content works at 320 CSS pixels wide (about 400 percent zoom) without scrolling in two directions, except content like maps or data tables.
The parts of controls and graphics needed to see or understand them, such as input borders, focus indicators and chart lines, have at least 3:1 contrast against adjacent colors.
Nothing is cut off or overlaps when users set line height to 1.5, paragraph spacing to 2, letter spacing to 0.12 and word spacing to 0.16 times the font size.
Tooltips and other content that appears on hover or focus can be dismissed, can be hovered over, and stays visible until the user moves away.
People can operate the interface: keyboard access, enough time, no seizure triggers, clear navigation and alternatives to complex gestures.
Guideline 2.1 Keyboard Accessible
Every function works with a keyboard, without precise keystroke timing, except input that depends on the path of movement, such as freehand drawing.
Keyboard focus never gets stuck: users can move focus away from every component with the keyboard, or are told how.
Every function works with a keyboard, with no exception for path-based input such as freehand drawing.
Single-key shortcuts (a letter, number, punctuation or symbol) can be turned off, remapped, or only work when the control has focus.
Guideline 2.2 Enough Time
Users can turn off, adjust or extend time limits, with narrow exceptions such as real-time events and limits over 20 hours.
Content that moves, blinks, scrolls or auto-updates on its own, such as a carousel or news ticker, can be paused, stopped or hidden.
Timing is not an essential part of any activity, except non-interactive media and real-time events.
Users can postpone or turn off interruptions such as alerts and updates, except in an emergency.
When a session expires, users can sign back in and continue without losing data.
Users are warned about inactivity timeouts that could lose data, unless the data is kept for more than 20 hours.
Guideline 2.3 Seizures and Physical Reactions
Nothing flashes more than three times in any one second, unless the flash is below the general and red flash thresholds.
Nothing flashes more than three times in any one second, with no threshold exception.
Motion animation triggered by interaction, such as parallax effects, can be turned off unless it is essential.
Guideline 2.4 Navigable
Users can skip blocks repeated on every page, such as the main navigation, with a skip link, landmarks or headings.
Each page has a title that describes its topic or purpose.
Keyboard focus moves through the page in an order that keeps its meaning and operation intact.
The purpose of each link is clear from its text, or from its text plus its context, such as the surrounding sentence or list item.
There is more than one way to find a page on the site, such as navigation, search or a site map.
Headings and labels describe the topic or purpose of what follows them.
Keyboard users can see which element has focus.
Users can tell where they are within the site, for example from breadcrumbs or a highlighted current page.
The purpose of each link can be identified from the link text alone.
Section headings organize the content.
A focused element is never completely hidden by your own content, such as a sticky header, footer or cookie banner.
No part of a focused element is hidden by your own content.
The focus indicator is at least as large as a 2 CSS pixel outline around the element and changes contrast by at least 3:1.
Guideline 2.5 Input Modalities
Anything done with multi-finger or path-based gestures, such as pinch or swipe, also works with a single tap or click.
Single-pointer actions do not fire on the down press, or can be aborted or undone, unless firing on press is essential.
A control's accessible name contains its visible label text, so voice control users can say what they see.
Functions triggered by shaking or tilting the device also work through regular controls, and the motion response can be turned off.
Pointer targets are at least 44 by 44 CSS pixels, with limited exceptions.
Content does not restrict which input methods, such as mouse, touch, keyboard or stylus, people can use.
Anything done by dragging also works with a single pointer without dragging, such as tapping or clicking.
Pointer targets are at least 24 by 24 CSS pixels or have enough space around them, with limited exceptions.
People can understand the content and the interface: a declared language, predictable behavior and help with input errors.
Guideline 3.1 Readable
The page's default language is set in code, for example with the lang attribute on the html element.
Passages in a different language from the rest of the page are marked with their language in code.
Users can find definitions of unusual words, idioms and jargon, for example in a glossary.
Users can find the expanded form or meaning of abbreviations.
Text that needs more than lower secondary reading ability has a simpler version or supporting content.
Users can find the pronunciation of words whose meaning depends on how they are pronounced.
Guideline 3.2 Predictable
Moving focus to an element does not trigger a change of context, such as opening a new window or submitting a form.
Changing a setting, such as picking a dropdown option, does not cause a change of context unless users are told first.
Navigation repeated across pages appears in the same relative order each time.
Components with the same function are labeled the same way across pages.
Changes of context happen only when the user asks for them, or users can turn them off.
Help options repeated across pages, such as contact details, a chat link or a help page, appear in the same relative order.
Guideline 3.3 Input Assistance
When an input error is detected automatically, the field in error is identified and the error is described in text.
Form fields and other inputs have labels or instructions.
When an input error is detected and a fix is known, the fix is suggested, unless that would undermine security or purpose.
Submissions that create legal or financial commitments, change stored data or submit test answers can be reversed, checked or confirmed.
Context-sensitive help is available, such as instructions next to a complex field.
Every form submission can be reversed, checked or confirmed, not only legal and financial ones.
Information users already gave in the same process is filled in or offered for selection instead of typed again, with exceptions such as security.
Signing in does not depend on remembering, transcribing or solving something unless there is an alternative, help such as paste and password manager support, or the test only asks users to recognize objects or their own content.
Like 3.3.8, but without the exceptions for recognizing objects or the user's own content.
Content works reliably with browsers and assistive technologies, now and as they change.
Guideline 4.1 Compatible
Buttons, form fields and custom widgets expose their name, role and current state to assistive technology.
Status messages, such as "Added to cart" or a search result count, are announced by screen readers without moving focus.
How to use this WCAG checklist
- Choose your target. Level AA is the usual goal. The DOJ's Title II rule for state and local governments uses WCAG 2.1 Level AA, due April 26, 2027 for governments serving 50,000 or more people and April 26, 2028 for smaller ones and special districts (Federal Register 2026-07663 (opens in new tab)). The Revised Section 508 Standards for federal agencies use WCAG 2.0 Level A and AA (36 CFR Part 1194 (opens in new tab)). Set the version switch above to match.
- Scan for the automatable failures first. Run the free WCAG checker on your key page templates, such as the home page, a product or service page, a form and checkout. It flags issues for the criteria marked Partly automated and shows how to fix them. For color pairs, the color contrast checker tests the 4.5:1 and 3:1 ratios in 1.4.3 and 1.4.11.
- Review the rest by hand. Use the site with only a keyboard, zoom to 200 and 400 percent, try a screen reader, check captions and transcripts, and submit forms with mistakes. Automated vs manual accessibility testing explains which checks need a person.
- Record and share progress. Tick each criterion as it passes, download the CSV for your team or audit file, and recheck after redesigns and major releases.
What changed in WCAG 2.2
W3C published WCAG 2.2 on 5 October 2023. It added 9 success criteria to WCAG 2.1 and removed 4.1.1 Parsing as obsolete, because assistive technology no longer parses HTML directly (W3C WCAG 2.2 (opens in new tab)). The new criteria:
- 2.4.11 Focus Not Obscured (Minimum) (Level AA)
- 2.4.12 Focus Not Obscured (Enhanced) (Level AAA)
- 2.4.13 Focus Appearance (Level AAA)
- 2.5.7 Dragging Movements (Level AA)
- 2.5.8 Target Size (Minimum) (Level AA)
- 3.2.6 Consistent Help (Level A)
- 3.3.7 Redundant Entry (Level A)
- 3.3.8 Accessible Authentication (Minimum) (Level AA)
- 3.3.9 Accessible Authentication (Enhanced) (Level AAA)
W3C states that content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0, though a policy that names 2.0 or 2.1 may still ask you to test and report 4.1.1. WCAG 2.2 is also an international standard, ISO/IEC 40500:2025 (opens in new tab). For examples and fixes for each new criterion, read WCAG 2.2 explained.
WCAG checklist FAQ
What is a WCAG checklist?
How many success criteria are in WCAG 2.2?
Which WCAG level and version do I need?
Is there a WCAG 2.1 or WCAG 2.0 checklist?
Can an automated tool check every WCAG criterion?
Can I download this WCAG checklist as a PDF or Excel file?
Does completing the checklist make my website ADA compliant?
Sources: W3C WCAG 2.2 (opens in new tab), Federal Register 2026-07663 (opens in new tab), DOJ web guidance (2022) (opens in new tab), 36 CFR Part 1194 (opens in new tab).
Test the automatable criteria now
Start with what a machine can check. The free WCAG checker scans a page against WCAG 2.2 Level AA rules with axe-core and shows how to fix each issue, so your manual review can focus on the criteria that need a person.
Run the free WCAG checkerGet WCAG Compliance Tips in Your Inbox
Receive checklist shortcuts, WCAG 2.2 updates, and compliance strategies.