ADA website compliance checklist 2026 (and why checkers alone are not enough)
Published: 8 min readThe AccessibleOrNot team
There is no official ADA website checklist. Title III of the Americans with Disabilities Act, which covers businesses open to the public, doesn't name a technical standard for websites; the US Department of Justice's 2022 guidance points to WCAG and the Section 508 Standards as helpful guidance. In practice, WCAG 2.1 Level AA is the most defensible target: it is the standard the DOJ adopted for state and local governments in April 2024, and the basis of the EU's standard for the European Accessibility Act. A checker can verify part of the list below automatically; the rest needs a keyboard, a screen reader and a person.
In short
- ADA Title III has no regulatory technical standard for websites; the DOJ's guidance of 18 March 2022 names WCAG and the Section 508 Standards as helpful guidance.
- ADA Title II (state and local governments) requires WCAG 2.1 AA; a 20 April 2026 interim final rule moved the deadlines to 26 April 2027 (population 50,000+) and 26 April 2028 (smaller entities and special districts).
- More than 5,000 ADA digital accessibility lawsuits were filed in 2025; nearly 70% targeted e-commerce, and 45% of federal cases named a company that had been sued before (UsableNet, January 2026).
- Automated checkers find about 57% of accessibility issues by volume (Deque, 2021); in the 16-item list below, 6 items can't be checked automatically at all.
What does the ADA require from a website?
The ADA requires businesses open to the public to give people with disabilities full and equal access to their goods and services. The DOJ has long taken the position that this includes what they offer online. What the law doesn't do, for private businesses, is name a technical standard. The DOJ's 2022 guidance says businesses have flexibility in how they comply, and that existing technical standards, WCAG and the Section 508 Standards, provide helpful guidance.
| ADA Title III | ADA Title II | EAA (EU) | |
|---|---|---|---|
| Who | Businesses open to the public (shops, restaurants, banks, healthcare, etc.) | State and local governments | Businesses selling certain products and services to EU consumers, including e-commerce |
| Technical standard | None in regulation; DOJ points to WCAG and Section 508 | WCAG 2.1 AA | EN 301 549 (web: WCAG 2.1 AA) |
| Dates | Applies now | 26 April 2027 (50,000+) / 26 April 2028 (smaller) | Since 28 June 2025 |
| Enforcement | Private lawsuits and the DOJ | The DOJ and complaints | Each member state's authority |
This post is not legal advice. Whether and how the ADA applies to a business based outside the US is a question for a US lawyer.
Source: US Department of Justice (DOJ), ADA.gov, Federal Register, Pacific ADA Center, EUR-Lex
Why do lawsuits matter more than the rule?
For private businesses, ADA web accessibility is mostly enforced through lawsuits, not inspections. UsableNet's analysis of 2025 filings, published on 8 January 2026:
- More than 5,000 ADA digital accessibility lawsuits in federal and state courts, about 3,100 of them in federal court and nearly 2,000 in New York and California state courts.
- Nearly 70% targeted e-commerce companies.
- 1,427 cases, 45% of federal filings, named a company that had already faced an ADA web accessibility claim.
- Lawsuits against companies using accessibility widgets continued all year, peaking above 150 in a single month.
The last two points are why a one-off fix isn't enough. A site that was fixed once and then drifted back through theme updates and new campaign pages can be sued again; a widget on top of unchanged code doesn't stop a claim about that code.
Source: UsableNet
The ADA website compliance checklist (WCAG 2.1 AA)
The 16 items below cover the WCAG 2.1 AA failures that most often block people on real sites. The last column says honestly whether an automated checker can verify the item.
| # | Check | WCAG 2.1 | Automated checker? |
|---|---|---|---|
| 1 | Every meaningful image has alt text that says what it shows; decorative images have alt="" | 1.1.1 (A) | Partly: finds missing alt, can't judge if it's right |
| 2 | Videos with speech have accurate captions | 1.2.2 (A) | Partly: finds a missing caption track, not wrong captions |
| 3 | Text contrast is at least 4.5:1 (3:1 for large text) | 1.4.3 (AA) | Mostly: unsure on text over images and gradients |
| 4 | Links in text aren't distinguished by colour alone | 1.4.1 (A) | Partly |
| 5 | Zoom isn't disabled; the page works at 200% and at 320 px width | 1.4.4, 1.4.10 (AA) | Partly: finds disabled zoom, not broken layouts |
| 6 | Everything works with a keyboard alone | 2.1.1 (A) | No |
| 7 | No keyboard trap in menus, pop-ups or the cart drawer | 2.1.2 (A) | No |
| 8 | Keyboard focus is always visible | 2.4.7 (AA) | No |
| 9 | Focus order follows the visual and logical order | 2.4.3 (A) | No |
| 10 | A skip link or landmarks let users bypass repeated blocks | 2.4.1 (A) | Yes |
| 11 | Each page has a descriptive title | 2.4.2 (A) | Partly: finds a missing title, not a vague one |
| 12 | Links and buttons have accessible names | 2.4.4, 4.1.2 (A) | Partly: finds empty ones, not unclear ones |
| 13 | The page language is set | 3.1.1 (A) | Yes |
| 14 | Form fields have visible labels | 1.3.1, 3.3.2 (A) | Yes |
| 15 | Form errors are described in text, next to the field | 3.3.1 (A) | No |
| 16 | Status messages ("added to cart") are announced to screen readers | 4.1.3 (AA) | No |
Two things aren't WCAG criteria but belong on the list: an accessibility statement that says what you've fixed and what's still open, and a working contact route for people who hit a barrier. A statement isn't proof of conformance; it shows a process.
Source: W3C, Deque Systems
Why aren't accessibility checkers enough on their own?
Count the last column: 3 items a checker can verify, 7 it can verify in part, 6 it can't verify at all. That matches the research. Deque's study of more than 2,000 audits found that automated testing caught about 57% of issues by volume; the W3C says evaluation tools can only assist, and human judgement is required.
The items a checker can't see are the ones that stop a purchase: a menu that won't open with a keyboard, a pop-up that traps focus, an error message that only turns a border red. These are also the kind of barriers a plaintiff's tester runs into on a checkout.
Use a checker for what it's good at: volume, location and repetition. It lists hundreds of instances of the same low-contrast price or unlabelled field in minutes, and tells you the next day if a theme update brings them back. Then spend human time on items 6–9, 15 and 16. Our post on the limits of automated testing has a 20-minute manual test for exactly these.
Source: Deque Systems, W3C WAI
A 30-day plan
- Week 1, scan: run an automated scan on each template (home, category, product, cart, checkout). Fix issues at template level first; one fix in a theme file can clear hundreds of instances.
- Week 2, test by hand: complete your main flow with a keyboard only, then with a screen reader (NVDA on Windows, VoiceOver on Mac and iPhone are free). Write down every place you get stuck.
- Week 3, fix: fix the manual findings in the component code, not with a widget. Rescan to check nothing broke.
- Week 4, document and monitor: publish an accessibility statement with a contact route, keep a dated record of what you fixed, and schedule a recurring scan. Consider an expert audit for your highest-risk flow.
What if you also sell into the EU or Türkiye?
WCAG 2.1 AA also covers the web part of the EAA, which has applied since 28 June 2025. Türkiye's Accessibility Circular (No. 2025/10) requires WCAG 2.2 Level A for e-commerce sites by 21 June 2027. If you build to WCAG 2.2 AA, one target covers all three. See our EAA guide for sellers outside the EU and the EAA overview.
Frequently asked questions
Is there an official ADA website compliance checklist?
No. ADA Title III doesn't set a technical standard for private websites. The DOJ's 2022 guidance points to WCAG and the Section 508 Standards; WCAG 2.1 AA is the most common practical target.
Does the ADA require WCAG 2.1 AA?
For state and local governments under Title II, yes, from 26 April 2027 or 26 April 2028 depending on size. For private businesses under Title III, no regulation names it, but it's the yardstick most often used.
Can an ADA compliance checker make my site compliant?
No. A checker finds the issues that can be detected automatically, about 57% by volume according to Deque. Keyboard access, focus, error messages and status messages need a human check.
Does an accessibility widget protect me from ADA lawsuits?
UsableNet's 2025 data shows lawsuits against companies using widgets continued all year, peaking above 150 in one month. A widget doesn't change the code a claim is about.
When are the ADA Title II web accessibility deadlines?
After the DOJ's interim final rule of 20 April 2026: 26 April 2027 for public entities serving 50,000 people or more, and 26 April 2028 for smaller entities and special district governments.
Sources
- Guidance on Web Accessibility and the ADA · US Department of Justice (DOJ), ADA.gov · 18 March 2022
- ADA Title II web and mobile app accessibility rule (Federal Register 2024-07758) · Federal Register · 24 April 2024
- DOJ delays ADA Title II Web and Mobile App Accessibility Rule compliance deadlines · Pacific ADA Center · April 2026
- ADA Web Lawsuit Trends for 2026: What 2025 Filings Reveal · UsableNet · 8 January 2026
- Automated testing study identifies 57 percent of digital accessibility issues · Deque Systems · 10 March 2021
- Selecting Web Accessibility Evaluation Tools · W3C WAI · 13 May 2024 (updated)
- WCAG 2.2 · W3C · 5 October 2023 (current version)
- Directive (EU) 2019/882 (European Accessibility Act) · EUR-Lex · 17 April 2019
- Presidential Circular No. 2025/10, Official Gazette No. 32933 (in Turkish) · Lexpera · 21 June 2025
Related articles
Tick off the automated half of the list today.
Enter your URL. We scan your templates, list the findings by severity with code examples, and add a manual checklist for the items a checker can't verify.