ADA website compliance in 2026: what actually matters
A plain-language guide to WCAG 2.2, demand letters, and the fixes to start with.
Key takeaways
- The ADA names no technical standard for private websites. WCAG is the leading technical benchmark, and courts and settlements often point to Level AA. Build to WCAG 2.2 AA and you cover the older versions too.
- Many demand letters start with an automated scan. In WebAIM's 2026 study, six failure types made up about 96% of automatically detected errors, but automated checks find only part of what WCAG covers.
- An overlay doesn't make a site compliant. A documented process puts you in a stronger position: audit, fix the code, test, publish a statement and keep dated records.
Does the ADA apply to your website?
Title III requires businesses that serve the public to give people with disabilities equal access. The law predates websites, but the Department of Justice's guidance on web accessibility and the ADA (opens in a new tab) says it covers what a business offers online.
If your site sells, takes bookings, collects leads or informs customers, plan as if the ADA applies. Plaintiff firms do.
The leading benchmark: WCAG 2.2 AA
WCAG is the leading technical benchmark for web accessibility, and Level AA is the level most laws, settlements and procurement rules reference. WCAG 2.2 (opens in a new tab) is the current version.
No federal rule names a version for private businesses, but the Justice Department adopted WCAG 2.1 AA as the Title II standard (opens in a new tab) for state and local governments in April 2024. More: the nine new WCAG 2.2 success criteria and our WCAG compliance page.
What changed for public websites in 2026
On April 20, 2026, the Justice Department extended the Title II dates by one year (opens in a new tab). The extension doesn't apply to private businesses.
| Public entity | New compliance date | Standard |
|---|---|---|
| Population of 50,000 or more | April 26, 2027 | WCAG 2.1 AA |
| Population under 50,000, and special districts | April 26, 2028 | WCAG 2.1 AA |
How demand letters and lawsuits actually work
Plaintiff firms scan many sites for detectable errors, then send a letter asking for remediation, attorney fees and sometimes monitoring. Many cases settle, often because defending can cost more.
- Federal court hears many cases, and New York, Florida and California are frequent venues.
- California state court adds the Unruh Act (opens in a new tab): at least $4,000 per violation, plus fees.
- Repeat claims are common: one settlement doesn't stop the next firm's scan.
Start with the most common failures
The 2026 WebAIM Million report (opens in a new tab) found detectable WCAG failures on 95.9% of the top million home pages. Six error types made up about 96% of the errors it detected:
| Failure | Share of home pages | Fix |
|---|---|---|
| Low-contrast text | 83.9% | 4.5:1 for body text, 3:1 for large text |
| Missing image alt text | 53.1% | Describe the image; empty alt if decorative |
| Missing form labels | 51% | A visible label tied to every input |
| Empty links | 46.3% | An accessible name on icon-only links |
| Empty buttons | 30.6% | A name a screen reader can announce |
| Missing page language | 13.5% | Set lang on the html element |
These are the errors software can detect. Automated checks cover only part of WCAG, so fixing these six is a strong start, not a measure of how much legal risk is left.
What an overlay or toolbar can and cannot do
ComplyMo ships an accessibility toolbar for text size and contrast, but a toolbar can't repair code: a menu on top rarely gives a nameless button a name.
In 2025 accessiBe agreed to pay $1 million (opens in a new tab) to settle FTC allegations that it misrepresented its product as able to make any site WCAG compliant. Hundreds of practitioners have signed the Overlay Fact Sheet (opens in a new tab).
A practical compliance workflow
- Audit. Scan your key templates against WCAG 2.2; ComplyMo site audits do it on a schedule and rank fixes.
- Fix in the code. Start with the six common failures, then keyboard and focus.
- Test by hand. Keyboard, screen reader and 200% zoom catch the traps scans miss.
- Publish a statement. The W3C has a statement generator (opens in a new tab).
- Monitor and keep dated records. Re-scan after releases; scans, fixes and test notes help you respond to a letter.
See how ComplyMo keeps that record on the ADA compliance page, or start a free trial and scan your site.
General information, not legal advice. Confirm your obligations with counsel.

