Home / Blog / ADA Compliance Checklist

ADA compliance checklist 2026: the complete WCAG guide

Every WCAG 2.1 Level AA requirement in plain English. Use this as your go-to reference for website accessibility. Then scan your site to see which ones you're actually passing.

How to use this checklist
Go through each section manually, or run a free automated scan to check most items instantly. Automated tools catch roughly 30–40% of issues; this checklist covers the rest that require human judgment.

Images & media

Every image has descriptive alt text
Not 'IMG_0234.jpg' — actual descriptions of what's in the image. Decorative images use alt="".
Videos have captions
All pre-recorded video content includes synchronized captions for deaf and hard-of-hearing users.
Videos have audio descriptions
Important visual information in videos is described in an audio track for blind users.
No auto-playing media
Audio and video don't play automatically — or provide controls to pause/stop within 3 seconds.

Color & contrast

Text meets 4.5:1 contrast ratio
Regular text against its background. This is the #1 violation on the web (79.1% of sites fail).
Large text meets 3:1 contrast ratio
Text 18px+ bold or 24px+ regular has a slightly relaxed requirement.
Color is not the only indicator
Don't use color alone to convey information (red = error). Add icons, text, or patterns.
UI components meet 3:1 contrast
Buttons, form fields, and interactive elements are distinguishable from their background.

Forms & inputs

Every input has a visible label
Not just placeholder text — an actual <label> element associated with the input.
Error messages are specific
'Email is required' not just 'Please fix errors.' Errors are programmatically associated with their fields.
Required fields are indicated
Both visually and programmatically (aria-required or required attribute).
Form instructions are provided before the form
If there's a specific format needed (MM/DD/YYYY), state it before the user reaches the field.

Navigation & keyboard

All functionality works with keyboard only
Every link, button, form field, and interactive element is reachable via Tab and activatable via Enter/Space.
Focus order is logical
Tab order follows the visual reading order — left to right, top to bottom.
Focus is visible
Users can see which element is currently focused. Never use outline: none without a replacement.
No keyboard traps
Users can Tab into AND out of every component. Modals, dropdowns, and menus must allow Escape to close.
Skip navigation link exists
A 'Skip to main content' link appears as the first focusable element for keyboard users.

Structure & semantics

Page has exactly one H1
And headings follow a logical hierarchy: H1 → H2 → H3. Don't skip levels.
Page language is declared
The <html> element has a lang attribute (e.g., lang="en"). 15.8% of sites miss this.
Landmarks are used correctly
<header>, <nav>, <main>, <footer>, and ARIA landmarks help screen readers navigate.
Lists use proper markup
Use <ul>/<ol>/<li> for lists, not styled <div> elements.
Tables have headers
Data tables use <th> elements with scope attributes. Layout tables should not be used.
Page title is descriptive
Each page has a unique, descriptive <title> that identifies the site and page content.

Links & buttons

Link text is descriptive
'Read our pricing guide' not 'Click here.' Screen reader users navigate by links — they need context.
Links are visually distinguishable
Underlined or otherwise clearly different from surrounding text. Not just color.
Buttons use <button> elements
Not <div onclick>. Native buttons get keyboard support and screen reader announcements for free.
No empty links or buttons
Every <a> and <button> has accessible text (visible text or aria-label). 45.4% of sites have empty links.

Dynamic content & ARIA

ARIA attributes are correct
If you use ARIA, use it correctly. Wrong ARIA is worse than no ARIA. Validate with a scanner.
Live regions announce updates
Content that changes dynamically (notifications, chat, search results) uses aria-live.
Modals manage focus
When a modal opens, focus moves to the modal. When it closes, focus returns to the trigger.
Custom widgets follow ARIA patterns
Tabs, accordions, date pickers, and carousels implement the correct ARIA design pattern.
Check your site against this list automatically
Our scanner tests most of these criteria in 60 seconds. See exactly what passes and what fails.
Run a free scan →
Related
How Much Does ADA Compliance Cost? →ADA Website Lawsuit: What Happens →