ADA website compliance in 2026: what actually matters
A plain-language guide to WCAG 2.2, demand letters, and the fixes that hold up.
Key takeaways
- The ADA does not name a technical standard for private business websites, but courts and settlements point to WCAG AA, and the Department of Justice cites WCAG as helpful guidance. Build to WCAG 2.2 AA and you cover the older versions too.
- Most demand letters start with an automated scan. The six failures that scanners find most often account for about 96% of detected errors, so fixing them removes most of your visible risk.
- An overlay or toolbar does not make a site compliant on its own. In 2025 the FTC ordered one overlay vendor to pay $1 million over claims that its tool made sites WCAG compliant.
- What holds up is a documented process: audit, fix the code, test with a keyboard and a screen reader, publish an accessibility statement, and keep dated records.
Does the ADA apply to your website?
Title III of the Americans with Disabilities Act requires businesses that serve the public, which the law calls places of public accommodation, to give people with disabilities equal access. The law was written in 1990, before websites mattered, so it says nothing about them directly.
The Department of Justice has taken the position for years that Title III covers the goods and services a business offers online. Its guidance on web accessibility and the ADA (opens in a new tab) says so plainly and tells businesses they have flexibility in how they comply, as long as the result is accessible.
Courts have not fully agreed on the edges. Some federal circuits require a connection between the website and a physical location, others do not. In practice that disagreement has not slowed lawsuits down, because plaintiffs file where the law is most favorable to them.
The standard everyone points to: WCAG 2.2 AA
The Web Content Accessibility Guidelines (WCAG) are published by the W3C. They describe testable requirements, called success criteria, grouped into three levels: A, AA and AAA. Level AA is the benchmark in nearly every law, settlement and procurement rule.
WCAG 2.2 (opens in a new tab) became a W3C Recommendation in October 2023. It keeps everything from WCAG 2.1, removes one obsolete criterion, and adds nine new ones, six of them at Level A or AA. Because it is backward compatible, a site that meets 2.2 AA also meets 2.1 AA and 2.0 AA.
For private businesses there is still no federal rule that names a version. For state and local governments there is: in April 2024 the Justice Department adopted WCAG 2.1 AA as the Title II standard (opens in a new tab). That rule is the clearest signal of what regulators consider reasonable, and settlements with private companies increasingly cite 2.1 or 2.2 AA.
If you want the detail on what changed in the latest version, read our guide to the nine new WCAG 2.2 success criteria, or the overview on our WCAG compliance page.
What changed for public websites in 2026
The Title II rule originally gave larger state and local governments until April 2026 to comply. On April 20, 2026, the Justice Department published an interim final rule extending those dates by one year (opens in a new tab).
| 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 |
The extension does not change the standard, and it does not apply to private businesses at all. Title III lawsuits against companies continued through the delay. If you build sites for public agencies, schools or utilities, the extra year is time to fix, not a reason to wait.
How demand letters and lawsuits actually work
Most accessibility claims against small and mid-sized businesses follow the same pattern. A plaintiff firm runs automated scans across many sites, finds pages with detectable errors, and sends a demand letter or files a complaint describing a disabled user who could not complete a task.
The letter usually asks for three things: a commitment to remediate, payment of attorney fees, and sometimes a monitoring period. Many cases settle quickly because defending them costs more than settling.
- Federal court is where most ADA Title III website cases are filed, with New York, Florida and California among the busiest districts.
- California state court adds the Unruh Civil Rights Act, which allows statutory damages of at least $4,000 per violation on top of fees.
- Repeat claims are common. A settlement with one firm does not stop another firm from scanning the same site next month.
The practical lesson: the errors that trigger letters are the ones a machine can find. That is also the good news, because a machine can find them for you first.
The fixes that hold up
Every year WebAIM scans the home pages of the top million websites. The 2026 WebAIM Million report (opens in a new tab) found detectable WCAG failures on 95.9% of them, an average of 56 errors per page, and six error types made up about 96% of everything detected.
| Failure | Share of home pages | How to fix it |
|---|---|---|
| Low-contrast text | 83.9% | Meet 4.5:1 for body text and 3:1 for large text; check brand colors on every background they appear on |
| Missing image alt text | 53.1% | Describe what the image communicates; use empty alt text for purely decorative images |
| Missing form labels | 51% | Give every input a visible label tied to it with a for attribute or by wrapping it |
| Empty links | 46.3% | Give icon-only links an accessible name, such as visually hidden text or aria-label |
| Empty buttons | 30.6% | Same fix as links: every button needs a name a screen reader can announce |
| Missing page language | 13.5% | Set the lang attribute on the html element |
Beyond those six, the issues that most often block real users are keyboard traps, focus that disappears or hides behind sticky headers, forms that clear themselves on error, and modals that screen readers cannot escape. None of them show up as colorful badges, which is why manual testing still matters.
Test the way users actually browse
- Put your mouse away and tab through your key journey: home, product, cart or form, confirmation. You should always see where focus is.
- Turn on a screen reader (VoiceOver on Mac, NVDA on Windows) and complete the same journey.
- Zoom the browser to 200% and check that nothing overlaps or disappears.
- Repeat after every significant release, not once a year.
What an overlay or toolbar can and cannot do
Accessibility toolbars, often called overlays, add a menu that lets visitors enlarge text, raise contrast, pause animation or switch to a more readable font. Those adjustments genuinely help some people, and ComplyMo ships one in its accessibility toolbar.
What a toolbar cannot do is repair the underlying code for everyone. Screen reader users bring their own assistive technology and depend on correct markup, labels and structure. If a button has no name in the HTML, a menu layered on top rarely fixes that reliably.
Regulators have noticed the gap between the marketing and the result. In 2025 the Federal Trade Commission finalized an order requiring accessiBe to pay $1 million (opens in a new tab) over claims that its automated product could make any website WCAG compliant. Hundreds of accessibility practitioners have also signed the Overlay Fact Sheet (opens in a new tab), which explains the limits of the approach.
A practical compliance workflow
You do not need a legal department to get this right. You need a repeatable process and proof that you follow it.
- Audit. Run an automated WCAG 2.2 scan across your important templates, not just the home page. The ComplyMo Agent does this on a schedule and ranks what to fix first.
- Fix in the code. Work through the six common failures, then the keyboard and focus issues from manual testing.
- Test with people and assistive technology. Keyboard, screen reader and zoom, on the journeys that make you money.
- Publish an accessibility statement. Say which standard you target, what you know is not yet fixed, and how to reach you. The W3C has a statement generator (opens in a new tab) if you want a template.
- Monitor. New content breaks things. Re-scan after releases and on a regular cadence.
- Keep dated records. Scan results, fixes and test notes are your best answer if a letter arrives.
That last step is the one most businesses skip, and it is the one that changes the conversation. A dated history showing you found and fixed issues is far stronger than a badge in the footer. See how ComplyMo keeps that record on the ADA compliance page, or start a free trial and scan your own site.
This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your obligations with counsel.
