Free tool · No sign-up
The interactive WCAG 2.2 checklist — and which parts a scanner can't do.
Work through all 55 WCAG 2.2 Level A & AA checks in plain English. Every item is tagged automated, partial or manual — so you see exactly what a tool catches and what still needs a human. Tick items off, filter by role, and print your record when you're done.
Automation catches a minority — this shows you which
A scanner reliably evaluates only a handful of these criteria (the green Automated tags) and flags candidates for some more (Partial). The rest — the majority — are human judgment: keyboard operation, focus order, reading order, meaningful alt text, error guidance. Filter to Manual to see exactly what a tool will never tell you.
1.1.1Non-text Content
Every meaningful image, icon and control has a text alternative; decorative images have empty alt.
1.2.1Audio-only & Video-only (Prerecorded)
Prerecorded audio-only has a transcript; video-only has a description or transcript.
1.2.2Captions (Prerecorded)
Prerecorded video with sound has synchronised captions.
1.2.3Audio Description or Media Alternative
Prerecorded video provides audio description or a full text alternative.
1.2.4Captions (Live)
Live audio/video streams carry real-time captions.
1.2.5Audio Description (Prerecorded)
Prerecorded video has audio description of important visual detail.
1.3.4Orientation
Content works in both portrait and landscape; orientation isn't locked.
1.3.5Identify Input Purpose
Common fields (name, email) use the right autocomplete tokens.
1.3.1Info and Relationships
Structure conveyed visually (headings, lists, tables, labels) is also in the markup.
1.3.2Meaningful Sequence
The reading and navigation order in the DOM matches the visual order.
1.3.3Sensory Characteristics
Instructions don't rely on shape, size or position alone ("click the round button").
1.4.1Use of Color
Color is never the only way to convey meaning (e.g. errors, links, required fields).
1.4.2Audio Control
Audio that plays for 3+ seconds can be paused, stopped or muted.
1.4.3Contrast (Minimum)
Body text has at least 4.5:1 contrast; large text at least 3:1.
1.4.4Resize Text
At 200% browser zoom, no content is lost, clipped or overlapping.
1.4.5Images of Text
Real text is used instead of images of text (except logos).
1.4.10Reflow
At 320px width, content reflows to one column with no horizontal scroll.
1.4.11Non-text Contrast
UI components, icons and focus indicators have at least 3:1 contrast.
1.4.12Text Spacing
Increasing line height and letter/word spacing doesn't clip or overlap text.
1.4.13Content on Hover or Focus
Tooltips/popovers are dismissable, hoverable and stay until dismissed.
2.1.1Keyboard
Every function works with the keyboard alone, no mouse required.
2.1.2No Keyboard Trap
Keyboard focus can always move away from any component.
2.1.4Character Key Shortcuts
Single-character shortcuts can be turned off, remapped, or are focus-only.
2.2.1Timing Adjustable
Time limits can be turned off, adjusted, or extended by the user.
2.2.2Pause, Stop, Hide
Moving, blinking or auto-updating content can be paused or stopped.
2.3.1Three Flashes or Below
Nothing flashes more than three times per second.
2.4.1Bypass Blocks
A skip link or landmarks let users bypass repeated navigation.
2.4.2Page Titled
Every page has a unique, descriptive <title>.
2.4.3Focus Order
Tab order follows a logical, meaningful sequence.
2.4.4Link Purpose (In Context)
Each link's purpose is clear from its text or immediate context.
2.5.1Pointer Gestures
Multipoint or path gestures have a single-pointer alternative.
2.5.2Pointer Cancellation
Actions fire on release, so a mistaken press can be aborted.
2.5.3Label in Name
A control's accessible name includes its visible label text.
2.5.4Motion Actuation
Motion-triggered functions (shake, tilt) have a UI alternative and can be disabled.
2.4.5Multiple Ways
There are at least two ways to reach each page (nav, search, sitemap).
2.4.6Headings and Labels
Headings and labels are descriptive and clear.
2.4.7Focus Visible
A visible focus indicator appears on every interactive element.
2.4.11Focus Not Obscured (Minimum)
Sticky headers/footers don't fully hide the focused element.
2.5.7Dragging Movements
Anything operated by dragging has a single-click/tap alternative.
2.5.8Target Size (Minimum)
Interactive targets are at least 24×24 CSS pixels or adequately spaced.
3.1.1Language of Page
The page's primary language is set with a lang attribute.
3.2.1On Focus
Moving focus to a component doesn't trigger an unexpected context change.
3.2.2On Input
Changing a field's value doesn't cause a surprising context change.
3.2.6Consistent Help
Help (contact, chat) appears in the same relative place across pages.
3.3.1Error Identification
Input errors are identified in text and clearly indicated.
3.3.2Labels or Instructions
Form fields have visible labels or clear instructions.
3.3.7Redundant Entry
Info entered earlier in a process is auto-filled or selectable, not re-typed.
3.1.2Language of Parts
Passages in another language are marked with the right lang attribute.
3.2.3Consistent Navigation
Navigation appears in the same order across pages.
3.2.4Consistent Identification
Components with the same function are labelled consistently.
3.3.3Error Suggestion
When an error is detected, a correction suggestion is offered.
3.3.4Error Prevention (Legal, Financial)
Legal/financial/data submissions are reversible, checked, or confirmable.
3.3.8Accessible Authentication (Minimum)
Login needs no memory/puzzle test; paste is allowed, passkeys/managers work.
4.1.2Name, Role, Value
Custom components expose a correct name, role and state to assistive tech.
4.1.3Status Messages
Status updates (cart, errors, toasts) are announced via aria-live.
Your results
Tick items as you verify them. Your progress saves in this browser and returns when you come back. When you're ready, print or save a PDF to share with your team or attach to an audit trail.
Of your unchecked items, 35 are manual-only — a scan can't see these. They need a keyboard, a screen reader, or human judgment.
Optional. We'll send a copy of your checklist state. No spam, unsubscribe anytime.
How to use this checklist
This is a self-assessment tool, not a substitute for a full audit — but it's the fastest way to see where you stand and to structure the work. A practical order:
Scan the Automated items
Filter to Automated + Partial and run a free scan to clear the high-volume basics fast.
Walk the Manual items
Filter to Manual and test with a keyboard and a screen reader on your key pages.
Split by role
Filter by Design, Dev or Content to hand each teammate just their items.
Print your record
Export a dated PDF as evidence of your conformance effort — useful for ADA, EAA and 508.
Each item links to our WCAG 2.2 guide for the detail behind it. For which version your law asks for, see the ADA, EAA and Section 508 guides.
Common questions
How many criteria are in a WCAG 2.2 Level AA checklist?
Level AA conformance means meeting the Level A criteria plus the Level AA criteria — 55 in total (31 at Level A, 24 at Level AA), after WCAG 2.2 removed 4.1.1 Parsing. This tool covers all 55, grouped by the four POUR principles.
Can an automated tool complete this for me?
No. Scanners reliably evaluate only a minority of criteria — contrast, page language, some name/role/value checks. The majority need human judgment: keyboard operation, focus order, reading order, meaningful alt text, error guidance. Each item is tagged so you can see which is which; a scan is the fast first pass, not the finish line.
Does this cover the ADA, EAA and Section 508?
Effectively yes. The ADA Title II rule and the EAA reference WCAG 2.1 AA, and Section 508 references WCAG 2.0 AA. Because WCAG 2.2 is backwards compatible, completing this 2.2 Level AA checklist also satisfies those earlier baselines.
Is my progress saved?
Yes, in your own browser. Ticked items are stored locally on your device, so your progress is there when you return. Nothing is uploaded, and you can reset any time. You can also print or save your results as a PDF.
Sources. W3C, WCAG 2.2 Recommendation (opens in a new tab) for all criteria and levels; automated-vs-manual classification informed by Deque's axe-core coverage data. Criterion levels verified against the W3C source. This tool is a self-assessment aid, not a certification or legal advice; a passing checklist is not a guarantee of conformance.
The manual items need eyes, not just a scan.
Start with a free automated scan to clear the fast wins, then bring in human testing for the criteria a tool can't judge. That's the honest path to real conformance.