ADA Website Compliance Checklist: All 55 WCAG 2.2 AA Criteria
The ADA doesn't publish a technical checklist for websites — courts use WCAG. This is every WCAG 2.2 Level A and AA success criterion, in plain English, with how each one is tested. Meeting all 55 also covers WCAG 2.1 AA.
- 55
- success criteria
- 31
- Level A
- 24
- Level AA
- 4
- principles
How to use this checklist
- Test your real templates — home, product, cart, checkout, forms, and blog — not just the homepage.
- Where a criterion is marked Automated, a tool can find some failures, but a person still has to confirm the rest.
- Anything without that mark needs a human: automated tools catch only 30–50% of WCAG issues.
Perceivable 20 criteria
Information can be seen, heard, or otherwise perceived. 9 Level A · 11 Level AA
1.1.1 Non-text Content
Level AEvery image, icon, and control has a text alternative that serves the same purpose; purely decorative images are hidden from screen readers.
How it's tested: AutomatedManual reviewScreen reader
1.2.1 Audio-only and Video-only (Prerecorded)
Level APrerecorded audio has a transcript, and silent video has a text or audio alternative.
How it's tested: Manual review
1.2.2 Captions (Prerecorded)
Level APrerecorded video with sound has accurate, synchronized captions.
How it's tested: Manual review
1.2.3 Audio Description or Media Alternative
Level APrerecorded video offers audio description or a full text alternative for what's only shown visually.
How it's tested: Manual review
1.2.4 Captions (Live)
Level AALive video with audio has real-time captions.
How it's tested: Manual review
1.2.5 Audio Description (Prerecorded)
Level AAImportant visual information in prerecorded video is described in audio.
How it's tested: Manual review
1.3.1 Info and Relationships
Level AHeadings, lists, tables, form labels, and groups are coded so their structure reaches assistive technology — not just the screen.
How it's tested: AutomatedManual reviewScreen reader
1.3.2 Meaningful Sequence
Level AThe reading order in the code matches the order that makes sense on screen.
How it's tested: Manual reviewScreen reader
1.3.3 Sensory Characteristics
Level AInstructions don't rely only on shape, size, position, or sound — no “click the round button on the right.”
How it's tested: Manual review
1.3.4 Orientation
Level AAContent works in both portrait and landscape unless one orientation is essential.
How it's tested: Manual review
1.3.5 Identify Input Purpose
Level AAFields that collect personal data (name, email, address) declare their purpose so browsers can autofill them.
How it's tested: AutomatedManual review
1.4.1 Use of Color
Level AColor is never the only way information is shown — for example, red-only error states or links set apart only by color.
How it's tested: AutomatedManual review
1.4.2 Audio Control
Level AAudio that plays automatically for more than 3 seconds can be paused or muted.
How it's tested: Manual review
1.4.3 Contrast (Minimum)
Level AAText has a contrast ratio of at least 4.5:1 against its background (3:1 for large text).
How it's tested: AutomatedManual review
1.4.4 Resize Text
Level AAText can be zoomed to 200% without losing content or functionality.
How it's tested: Manual review
1.4.5 Images of Text
Level AAReal text is used instead of pictures of text, except for logos.
How it's tested: Manual review
1.4.10 Reflow
Level AAContent fits a 320-pixel-wide screen without horizontal scrolling — the equivalent of 400% zoom.
How it's tested: Manual review
1.4.11 Non-text Contrast
Level AAIcons, input borders, focus indicators, and other interface parts have at least 3:1 contrast.
How it's tested: Manual review
1.4.12 Text Spacing
Level AANothing breaks when users increase line, letter, word, and paragraph spacing.
How it's tested: Manual review
1.4.13 Content on Hover or Focus
Level AATooltips and pop-ups that appear on hover or focus can be dismissed, can be hovered, and stay visible until the user moves on.
How it's tested: Manual reviewKeyboard
Operable 20 criteria
Everything works with a keyboard, with time, without traps. 14 Level A · 6 Level AA
2.1.1 Keyboard
Level AEverything works with a keyboard alone: menus, forms, carts, modals, sliders, and checkout.
How it's tested: Keyboard
2.1.2 No Keyboard Trap
Level AKeyboard focus can always move away from any component — nothing traps it.
How it's tested: Keyboard
2.1.4 Character Key Shortcuts
Level ASingle-key shortcuts can be turned off or remapped so they don't fire by accident.
How it's tested: Manual reviewKeyboard
2.2.1 Timing Adjustable
Level ATime limits, like checkout or session timeouts, can be turned off, adjusted, or extended.
How it's tested: Manual review
2.2.2 Pause, Stop, Hide
Level ACarousels, auto-scrolling content, and animations that run longer than 5 seconds can be paused.
How it's tested: Manual review
2.3.1 Three Flashes or Below Threshold
Level ANothing flashes more than three times per second.
How it's tested: Manual review
2.4.1 Bypass Blocks
Level AA skip link or landmarks let users jump past repeated navigation.
How it's tested: AutomatedKeyboardScreen reader
2.4.2 Page Titled
Level AEvery page has a title that describes its topic or purpose.
How it's tested: AutomatedManual review
2.4.3 Focus Order
Level AKeyboard focus moves through the page in an order that preserves meaning.
How it's tested: Keyboard
2.4.4 Link Purpose (In Context)
Level AThe purpose of every link is clear from its text or context — no bare “click here.”
How it's tested: AutomatedManual reviewScreen reader
2.4.5 Multiple Ways
Level AAThere's more than one way to find a page, such as navigation, search, or a sitemap.
How it's tested: Manual review
2.4.6 Headings and Labels
Level AAHeadings and labels describe the topic or purpose of what follows.
How it's tested: Manual review
2.4.7 Focus Visible
Level AAYou can always see which element has keyboard focus.
How it's tested: Keyboard
2.4.11 Focus Not Obscured (Minimum)
Level AAThe focused element isn't completely hidden by sticky headers, cookie banners, or chat widgets.
How it's tested: Keyboard
2.5.1 Pointer Gestures
Level AAnything that needs a multi-finger or path gesture, like pinch or swipe, also works with a single tap or click.
How it's tested: Manual review
2.5.2 Pointer Cancellation
Level AActions fire when the pointer is released, not pressed, so accidental taps can be undone.
How it's tested: Manual review
2.5.3 Label in Name
Level AA control's accessible name includes its visible label, so voice-control users can say what they see.
How it's tested: AutomatedManual reviewScreen reader
2.5.4 Motion Actuation
Level AFeatures triggered by shaking or tilting the device also work through the interface and can be disabled.
How it's tested: Manual review
2.5.7 Dragging Movements
Level AAAnything done by dragging — sliders, sortable lists, maps — can also be done without dragging.
How it's tested: Manual review
2.5.8 Target Size (Minimum)
Level AAClick and tap targets are at least 24 × 24 CSS pixels, or have enough space around them.
How it's tested: AutomatedManual review
Understandable 13 criteria
Content and forms behave predictably and explain errors. 7 Level A · 6 Level AA
3.1.1 Language of Page
Level AThe page declares its main language so screen readers pronounce it correctly.
How it's tested: Automated
3.1.2 Language of Parts
Level AAPassages in another language are marked up — for example, a Spanish section on an English page.
How it's tested: Manual reviewScreen reader
3.2.1 On Focus
Level AMoving focus to an element never triggers an unexpected change, like a pop-up or a new page.
How it's tested: Keyboard
3.2.2 On Input
Level AChanging a setting, like a dropdown, doesn't unexpectedly change context unless users are told first.
How it's tested: Manual reviewKeyboard
3.2.3 Consistent Navigation
Level AANavigation that repeats across pages appears in the same order every time.
How it's tested: Manual review
3.2.4 Consistent Identification
Level AAComponents with the same function are labeled the same way across the site.
How it's tested: Manual review
3.2.6 Consistent Help
Level AHelp options — contact details, chat, phone — appear in the same place on every page.
How it's tested: Manual review
3.3.1 Error Identification
Level AForm errors are identified and described in text, not only with color or an icon.
How it's tested: Manual reviewScreen reader
3.3.2 Labels or Instructions
Level AEvery form field has a visible label or instructions.
How it's tested: AutomatedManual review
3.3.3 Error Suggestion
Level AAWhen an input error is detected, the site suggests how to fix it where it can.
How it's tested: Manual review
3.3.4 Error Prevention (Legal, Financial, Data)
Level AAOrders, payments, and legal submissions can be reviewed, corrected, or reversed before they're final.
How it's tested: Manual review
3.3.7 Redundant Entry
Level AUsers aren't asked to re-enter information they already gave in the same process, like a shipping address.
How it's tested: Manual review
3.3.8 Accessible Authentication (Minimum)
Level AALogging in doesn't require a memory or transcription test unless there's an alternative — password managers and paste must work.
How it's tested: Manual review
Robust 2 criteria
Assistive technology can read and operate it. 1 Level A · 1 Level AA
4.1.2 Name, Role, Value
Level ACustom controls — menus, tabs, toggles, modals — expose their name, role, and state to assistive technology.
How it's tested: AutomatedManual reviewScreen reader
4.1.3 Status Messages
Level AAMessages like “Added to cart” or “3 results found” are announced by screen readers without moving focus.
How it's tested: Manual reviewScreen reader
Don't want to check 55 criteria yourself?
We audit your site by hand against every item on this list, rank the issues by risk, and fix them in your code — with a before-and-after report as proof.
ADA website compliance checklist FAQ
Which WCAG version does the ADA require?
The ADA doesn't name a version for business websites. U.S. courts use WCAG 2.1 Level AA as the benchmark, and WCAG 2.2 AA — the current W3C recommendation — is best practice. Meeting 2.2 AA also covers the 2.1 AA criteria, which is why this checklist uses it.
What changed in WCAG 2.2?
WCAG 2.2 added six Level A and AA criteria to 2.1: Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size (2.5.8), Consistent Help (3.2.6), Redundant Entry (3.3.7), and Accessible Authentication (3.3.8). It also removed 4.1.1 Parsing, which is now obsolete.
Can an automated checker complete this checklist?
No. Automated tools catch only 30–50% of WCAG issues. They can flag missing alt text or low contrast, but not whether alt text is meaningful, whether focus order makes sense, or whether a screen reader can complete your checkout. Most of this list needs a person.
Is this checklist enough to make my website ADA compliant?
It's the complete list of what WCAG 2.2 AA requires, but checking it properly takes manual code inspection, keyboard testing, and screen-reader testing on every template. If you'd rather not do it yourself, we audit every criterion and fix the issues in your code.
How do you make a website ADA compliant?
You bring it into WCAG 2.1/2.2 AA conformance at the code level: fixing color contrast, adding meaningful image alt text, labeling forms, and ensuring full keyboard and screen-reader operability. Automated tools find only 30–50% of issues, so a manual audit is required to do it properly.
Start here
Get all 55 criteria checked on your site
Real issues, ranked by risk, with a clear remediation plan.
Prefer to talk? Call +1 (786) 793-6135 or message us on WhatsApp (opens in a new tab).