The short version
- The Americans with Disabilities Act (ADA) has been applied to business websites. The Department of Justice says sites open to the public must be accessible.
- There is no single law that lists exact rules for private sites — but courts and regulators consistently point to one technical standard: WCAG, Level AA.
- Most claims start as a demand letter, not a courtroom. Reported settlements commonly run $5,000–$25,000, and most are paid quietly.
- Accessibility overlay widgets do not make you compliant — businesses using them are still sued.
- The durable fix is a site built to WCAG 2.2 AA, with a published accessibility statement and an audit you can point to.
What "ADA website compliance" actually means
"ADA compliance" for a website is shorthand for one idea: a person with a disability should be able to use your site as effectively as anyone else. Someone who is blind and uses a screen reader, someone who can't use a mouse, someone with low vision or a tremor — they should all be able to read your hours, fill out your form, and book an appointment.
When people say a site is "ADA compliant," what they really mean is that it conforms to a published technical standard called WCAG — the Web Content Accessibility Guidelines. The ADA itself never mentions WCAG, websites, or alt text. That gap between a 1990 civil-rights law and a 2026 website is exactly where the confusion — and the litigation — lives.
"The ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web."
Does the ADA apply to your website?
For most businesses, the practical answer is yes. Here is the reasoning courts use:
- Title III of the ADA prohibits discrimination by "places of public accommodation" — a broad category that includes shops, restaurants, offices of healthcare providers, spas, and professional services. 2
- The DOJ's position is that a public accommodation's website is covered, even though the statute predates the web. 1
- Courts have largely agreed, particularly where a website connects to a physical place of business — which describes nearly every local practice and storefront.
In April 2024, the DOJ issued a final rule requiring state and local governments to meet WCAG 2.1 Level AA. 3 That rule is for Title II (government), not private business — but it is the clearest signal yet of where the federal benchmark is settling, and plaintiff attorneys cite it.
The standard everyone points to: WCAG 2.2 AA
The Web Content Accessibility Guidelines are published by the World Wide Web Consortium (W3C). WCAG 2.2 became the recommended version in October 2023. 4 The guidelines come in three conformance levels — A, AA, and AAA — and AA is the level the legal world treats as the bar.
Every guideline rolls up to four plain-language principles, known by the acronym POUR:
Perceivable
People can perceive the content — alt text on images, captions, enough color contrast.
Operable
Everything works by keyboard, not just a mouse. Nothing traps or rushes the user.
Understandable
Text is readable, forms have clear labels, and errors are explained.
Robust
The code is clean enough that assistive technology can read it reliably.
Building to 2.2 AA covers everything in the older 2.1 AA that the DOJ adopted, plus newer criteria — so it is the safest target today.
Conformance vs. compliance — and why the difference matters
These two words get used as if they mean the same thing. They don't — and the gap between them is where a lot of misleading marketing lives.
Conformance
A technical status. Your site either meets the specific, testable success criteria of a standard — WCAG 2.2 Level AA — or it doesn't. It is measurable, you can audit it, and you can honestly claim it.
Compliance
A legal status. Whether you have met the obligations of a law — the ADA. It is decided by courts and regulators in the full context of your business, not by a scanner or a vendor.
Put simply: you conform to WCAG; you comply with the ADA. WCAG 2.2 AA conformance is the evidence you use to demonstrate ADA compliance — the strongest evidence available — but no tool, plugin, or agency can hand you a guarantee of legal "compliance."
The real risk: demand letters, not just lawsuits
The headline number — thousands of website accessibility lawsuits filed each year — undercounts the problem. According to industry tracking of federal and state filings, several thousand digital-accessibility cases are filed annually in the U.S. 5 But the lawsuits are the visible tip. The much larger volume is demand letters that settle privately and never appear in any court record.
Thousands
of digital ADA lawsuits filed in the U.S. each year 5
$5K–$25K
commonly reported range to settle a single demand letter 6
~30 days
a typical window a demand letter gives you to respond
The economics favor the sender. A scanner finds violations automatically, a templated letter goes out, and settling is cheaper and faster than fighting — so most businesses pay. The trap: after you settle, your site is still broken. You can be approached again, and you still have to remediate. You pay twice.
Estimate your exposure
Answer six questions for a rough, transparent estimate of your risk level and what a demand-letter event could cost. Nothing is sent anywhere — this runs entirely in your browser.
The handful of violations behind most claims
Automated scanners look for the same small set of failures over and over, because they are common, easy to detect, and clearly tied to WCAG. If your site has these, you are findable:
| The violation | Why it fails |
|---|---|
| Missing alt text | A screen reader can't describe an image with no text alternative. |
| Low color contrast | Light-gray text on white fails the 4.5:1 contrast minimum. |
| Unlabeled form fields | An input with no label is unusable by assistive technology. |
| Empty links & buttons | An icon-only button with no accessible name announces nothing. |
| No keyboard access | Menus and forms that only work with a mouse trap keyboard users. |
| No accessibility statement | Not a WCAG failure itself, but its absence signals an easy target. |
Why accessibility overlays don't make you compliant
An overlay is a script you paste onto your site that adds a floating accessibility toolbar. Vendors market them as one-line compliance. In practice they sit on top of broken code without fixing it — and they have become a warning sign rather than a shield.
- Businesses with overlays installed are still sued. Plaintiffs and their experts test the underlying page, not the widget.
- Many screen-reader users actively dislike them, and accessibility advocates broadly recommend against them.
- The FTC has taken enforcement action against an overlay vendor over deceptive accessibility claims. 7
The only thing that holds up is accessibility built into the page itself.
How to actually become compliant
There are two honest paths. Which fits depends on how much of your site can be salvaged.
- Audit honestly. Run an automated check (free tools like WAVE or axe catch a lot), then test by keyboard and with a screen reader. Automated tools find maybe a third of issues — the rest need a human.
- Remediate or rebuild. Fix contrast, labels, alt text, headings, and keyboard support in the code. If the site is a heavy CMS-and-plugin stack, a clean rebuild is often cheaper than chasing failures across templates.
- Document it. Publish an accessibility statement and your audit results. This is what gives you a defensible position if anyone asks.
- Maintain it. Compliance is a state, not an event. Every new page or plugin update can reintroduce a failure, so re-test on change.
Frequently asked questions
Does the ADA really apply to my business website?
For most public-facing businesses, yes. The DOJ has stated the ADA covers the websites of public accommodations, and that category includes the great majority of local businesses and healthcare practices. 1
What exact standard do I have to meet?
There's no single private-sector technical regulation yet, but courts, the DOJ, and settlements consistently reference WCAG Level AA. WCAG 2.1 AA is the practical floor; building to WCAG 2.2 AA covers it and the newer criteria. 3
Will an overlay widget protect me?
No. Overlays don't reliably fix the underlying code, sites using them are still sued, and the FTC has acted against an overlay vendor for deceptive claims. 7
Can I still get a demand letter if my site is compliant?
Nothing makes you immune. But a documented, conformant site with a published statement and audit history is far less attractive to target and gives you a strong position if approached.
Is this legal advice?
No. This guide is educational and standards-based. For your specific obligations and risk, consult a qualified attorney.
Sources & references
- U.S. Department of Justice, Civil Rights Division — Guidance on Web Accessibility and the ADA (2022).
- Americans with Disabilities Act, Title III — ada.gov.
- U.S. DOJ final rule, Title II — Accessibility of Web Content and Mobile Apps (WCAG 2.1 AA), April 2024.
- W3C / WAI — Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, Oct 2023.
- Industry litigation tracking of federal & state ADA digital filings (e.g. UsableNet annual reports). Figures vary year to year — verify the latest before citing a specific number.
- Commonly reported settlement, legal, and remediation ranges aggregated from accessibility-law practitioners and published settlement summaries. Directional, not a quote.
- U.S. Federal Trade Commission enforcement action against an accessibility-overlay vendor over deceptive claims (2025).
Editorial note: statistics in this guide are reviewed periodically. Where a precise figure matters for your decision, follow the linked primary source for the current number.
About this guide
This reference is written and maintained by Marcel Bessen, a DHS Trusted Tester (in progress) and the founder of castara.io, an accessible-website service. It is written to be standards-based and vendor-neutral: the law and the WCAG guidance it describes apply no matter who builds your site. Every claim is reviewed against primary sources from the DOJ, ada.gov, and the W3C, and updated as guidance and case law evolve.
This article is part of the castara.io Guide — a growing, plain-English library on ADA and WCAG for U.S. business owners, published at castara.io/guide. New guides are added over time; the changelog below tracks substantive updates.
Changelog
- — Added the interactive risk calculator; refreshed litigation figures and DOJ rule references.
- — Expanded the overlays section after FTC enforcement news.
- — First published.