Yes — for most businesses, ADA compliance is effectively required for websites. The Department of Justice has long taken the position that the Americans with Disabilities Act covers business websites, and most courts agree — even though no federal regulation spells out a technical standard for private companies. In practice, courts and settlement agreements treat WCAG, the Web Content Accessibility Guidelines, as the benchmark. If your website serves the public, the safest legal assumption in 2026 is that the ADA applies to it.
That short answer hides some genuinely messy law. Here is what is actually written down, what courts have decided, and what it means for your business right now.
What does the ADA actually say about websites?
Almost nothing, literally. The ADA predates the commercial web, and Title III — the part that applies to private businesses — requires “places of public accommodation” to be accessible without ever mentioning the internet.
That gap is the source of most of the confusion. There is no formal federal regulation telling a private business which technical standard its website must meet. But the absence of a regulation is not the absence of an obligation: the DOJ’s longstanding position is that business websites are covered under the ADA, and most courts to consider the question have agreed.
Is ADA compliance required for websites according to the courts?
The case most people cite is Robles v. Domino’s Pizza. In 2019, the Ninth Circuit held that the ADA applies to a website and app connected to physical locations, and the Supreme Court declined to review the decision — leaving it standing. The landmark came even earlier: National Federation of the Blind v. Target settled in 2008 with a $6 million class fund plus a remediation commitment.
One appellate decision briefly went the other way. Gil v. Winn-Dixie (11th Cir. 2021) held that a website was not a place of public accommodation, but the ruling was later vacated, and the split between circuits remains unresolved. In practice, that split doesn’t protect you — plaintiffs simply file in the courts that favor them, and the settlement math rarely changes.
Didn’t the DOJ pass a web accessibility rule?
Yes — but for governments, not businesses. In April 2024 the DOJ published a final rule under Title II adopting WCAG 2.1 AA as the required standard for state and local government websites and mobile apps. In April 2026 the DOJ extended the compliance deadlines: entities serving 50,000 or more people now have until April 26, 2027; smaller entities and special districts have until April 26, 2028.
If you run a private business, that rule does not bind you directly — but it matters anyway. It confirms the DOJ’s view that the ADA reaches digital content, and it signals exactly which technical standard regulators consider reasonable. We break down the details in our guide to the DOJ’s web accessibility rule.
Why do state laws raise the stakes?
Federal Title III claims get plaintiffs injunctive relief and attorney’s fees — not damages. State laws are where the money is.
- California. The Unruh Act sets minimum statutory damages of $4,000 per violation plus attorney’s fees, and a 1992 amendment makes any ADA violation automatically an Unruh violation. That combination is why California demand letters are so common.
- New York. State and city human-rights laws layer on top of the ADA, and New York leads the nation in state-court web-accessibility filings.
- Florida. The most active state for federal web-accessibility filings.
What standard does your website actually have to meet?
The de facto answer is WCAG, at conformance Level AA. WCAG comes in three levels: A is the minimum, AA is the level courts, the DOJ rule, and European regulators all reference, and AAA is aspirational. The current version, WCAG 2.2, became a W3C Recommendation in October 2023, and WCAG 2.2 AA is the benchmark ADA Fail audits against.
Selling to EU consumers adds a second layer. The European Accessibility Act, enforceable since June 2025, explicitly covers e-commerce and points to a technical standard that incorporates WCAG 2.1 AA — and US companies selling into the EU are in scope.
What happens if you do nothing?
Statistically, you are exposed. More than 5,000 digital-accessibility lawsuits were filed in 2025 — up roughly 20% over 2024 — and e-commerce sites drew about 70% of them. Most cases settle for between $10,000 and $75,000 plus a remediation commitment, which means you end up paying for the fix and the lawsuit.
Exposure is also nearly universal. WebAIM’s 2025 analysis of the top one million homepages found detectable WCAG failures on 94.8% of them — mostly low-contrast text, missing image alt text, missing form labels, and empty links or buttons. Those are exactly the errors automated scans catch, which is why serial plaintiffs find targets so easily. A free accessibility audit will tell you in plain English whether your site is carrying any of them.
Can a widget or overlay handle this for you?
No script fixes a broken website, and the FTC has now said so with a fine attached: in January 2025 it announced a $1 million action against accessiBe, alleging the company deceptively claimed its widget could make any website WCAG-compliant. The National Federation of the Blind formally opposes overlay products, calling them not only ineffective but harmful, and UsableNet’s reporting repeatedly finds hundreds of companies sued each year already had a widget or overlay installed.
One distinction matters here. A user-preference widget — contrast and text-size controls on a site that is already accessible at the code level, making no compliance claims — is a legitimate convenience; ADA Fail’s own site runs one. A “compliance” overlay sold as a substitute for fixing your code is a different product entirely. The claim is the problem, not the button. We unpack the difference in our comparison of accessibility widgets vs. overlays.
What should a business owner do next?
- Get a baseline. Find out what an automated scan flags on your site — and remember that automated tools can detect only about a third of WCAG success criteria. The rest requires human testing with keyboards and screen readers.
- Fix issues at the code level. Contrast, alt text, form labels, and keyboard access are engineering work, not settings toggles.
- Keep it fixed. Every redesign, plugin update, and new page can introduce regressions, so monitoring matters as much as remediation.
Already received a demand letter? Don’t ignore it, and don’t panic-install an overlay. Read our guide on what to do when an ADA demand letter arrives first.
The bottom line: the safest reading of the law in 2026 is that yes, the ADA applies to your website — and getting ahead of it costs far less than settling. Start with a free WCAG 2.2 audit from ADA Fail: we’ll show you exactly what a plaintiff’s scan would find on your site and what it takes to fix it.
Frequently asked questions
Does the ADA apply to small business websites too?
Yes. Title III has no small-business exemption for places of public accommodation — a two-person shop with an online store faces the same legal theory as a national retailer. Serial plaintiffs routinely target small businesses precisely because they tend to settle quickly rather than fund a defense.
Is WCAG itself a law?
No. WCAG is a set of technical guidelines published by the W3C, a standards body — it is not legislation. But it functions as the legal benchmark: courts and settlements reference it under the ADA, the DOJ’s Title II rule adopts WCAG 2.1 AA for governments, and the EU’s technical standard incorporates it. Conforming to WCAG 2.2 AA, verified through expert human testing, is the strongest position a business can put itself in.
Do I need to worry if my business has no physical location?
You still carry real risk. Some courts tie ADA coverage to a connection with a physical place, but others do not, and state laws — New York’s human-rights laws, California’s Unruh Act — reach online-only businesses. The filing data bears this out: e-commerce, much of it online-only, accounts for roughly 70% of web-accessibility suits.