ADA website compliance checklist
There's no single codified ADA technical standard for websites — but US courts and DOJ settlement agreements consistently point to WCAG. Here's a plain-English checklist built from WCAG 2.2 Level AA, the version that meets and exceeds current settlement practice.
Why WCAG 2.2 AA, if the ADA doesn't name a standard
Title III of the Americans with Disabilities Act applies to websites of "public accommodations" — that's DOJ's long-standing position — but DOJ has not finalized website-specific regulations, so there's no single legally codified technical standard the way the EU's European Accessibility Act has EN 301 549. In practice, US courts and DOJ settlement agreements and consent decrees most commonly reference WCAG 2.0 or 2.1 Level AA as the de facto compliance benchmark. Building to WCAG 2.2 AA — the current version — meets and exceeds that common practice.
This is informal legal practice shaped by litigation and settlement patterns, not a formal regulatory requirement, and it can change as case law or DOJ rulemaking develops. It is not legal advice.
20 checks to run today
These are pulled directly from our WCAG 2.2 self-audit checklist — 20 of the 55 total rows, chosen because they're the checks most likely to appear in an ADA demand letter or a quick plaintiff's-side scan. Mark each Pass, Fail, or N/A as you go.
| # | Check | Level | How to test |
|---|---|---|---|
| 1.1.1 | Every image, icon, and non-text element has appropriate alt text (or is marked decorative). | A | Inspect alt attributes; run an automated scanner. |
| 1.3.1 | Headings, lists, tables, and form labels are marked up semantically, not just styled to look that way. | A | Inspect DOM structure; confirm a screen reader announces it correctly. |
| 1.4.1 | Color is never the only way information is conveyed (errors, required fields, links). | A | View the page desaturated; confirm meaning still reads. |
| 1.4.3 | Text has at least 4.5:1 contrast (3:1 for large text) against its background. | AA | Run axe DevTools/WAVE or a contrast checker. |
| 1.4.4 | Text can be resized to 200% without loss of content or function. | AA | Zoom the browser to 200%; check for clipped content. |
| 1.4.10 | Content reflows to one column at 320px width without horizontal scrolling. | AA | Resize viewport to 320px; check for horizontal scroll. |
| 2.1.1 | Every function is operable with a keyboard alone. | A | Unplug the mouse; Tab/Enter/Space through the whole page. |
| 2.1.2 | Keyboard focus is never trapped in a component with no way out. | A | Tab into modals/widgets; confirm Esc or Tab escapes. |
| 2.2.2 | Moving, blinking, or auto-updating content can be paused or stopped. | A | Locate carousels/auto-updating content; check for a pause control. |
| 2.4.1 | A skip link or landmark lets users bypass repeated blocks of content. | A | Load the page, press Tab once; confirm a "Skip to content" link appears. |
| 2.4.2 | Every page has a descriptive, unique title. | A | Check the browser tab title on each page template. |
| 2.4.4 | Link text (with surrounding context) makes the link's purpose clear — no bare "click here." | A | Scan link text against its surrounding sentence. |
| 2.4.7 | A visible keyboard-focus indicator appears on every interactive element. | AA | Tab through the page; confirm a visible focus ring on each control. |
| 2.5.8 | Interactive targets are at least 24×24 CSS pixels, or have sufficient spacing. | AA | Measure button/icon touch targets in dev tools. |
| 3.1.1 | The page's primary language is set in code. | A | Inspect the lang attribute on <html>. |
| 3.3.1 | Form errors are identified in text, not color alone. | A | Submit a form with an error; check the error is described in text. |
| 3.3.2 | Form fields have visible labels or instructions. | A | Review every field for an associated, visible label. |
| 3.3.8 | Login doesn't require solving a puzzle or memorizing/transcribing text, unless an alternative exists. | AA | Review the login flow; confirm password managers/copy-paste work. |
| 4.1.2 | Custom widgets (dropdowns, tabs, modals) expose correct name/role/state to assistive tech. | A | Inspect the accessibility tree in dev tools. |
| 4.1.3 | Status messages (form submitted, item added to cart) are announced without moving focus. | AA | Trigger a status update; confirm an ARIA live region announces it. |
What the full checklist adds
The list above is 20 of the 55 active WCAG 2.2 Level A + AA success criteria (WCAG 2.2 formally removed the old "4.1.1 Parsing" entry — if you see a kit or reference claiming 56, they're still counting it). The full self-audit checklist in AccessibleDocs Kit covers all 55, organized the same way, plus:
- All remaining Perceivable, Operable, Understandable, and Robust criteria — including timing, seizure-safety, and consistent-navigation checks not shown here
- A Pass/Fail/N-A column and notes field per row, ready to fill in and hand to a developer or auditor
- A remediation plan template with severity tiers (Critical/High/Medium/Low) and suggested deadline SLAs, so a failed check turns into a tracked, owned fix
- An accessibility statement template to publish your honest conformance status once you've run the audit
Get all 55 checks, plus the remediation plan to act on them
Core Kit: full WCAG 2.2 self-audit checklist, remediation plan template, accessibility statement (EU + US), and internal policy — $99, one-time.
Get Core — $99 Compare Core vs ProFAQ
Is there an official ADA website compliance checklist from the government?
No. The DOJ has not published a website-specific technical standard or checklist for ADA Title III. This checklist is built from WCAG 2.2 Level AA — the standard most commonly referenced in ADA settlements and consent decrees — as the practical, defensible benchmark to test against.
Do I need WCAG AAA to be ADA compliant?
Almost never for commercial sites. Level AAA (31 additional criteria) is rarely required by law, regulation, or contract and is generally treated as aspirational. AA is the de facto commercial standard referenced in ADA settlement practice and EU EAA compliance alike.
Is passing this checklist a legal guarantee against an ADA lawsuit?
No. No checklist or product can guarantee that. Passing it substantially reduces the "no accessibility program at all" exposure that most ADA web-accessibility suits target, and gives you documented, defensible evidence of a good-faith effort. This is not legal advice — consult qualified counsel for your specific situation.