Yes — a small business can absolutely be sued over an inaccessible website, and it happens thousands of times a year. Courts in much of the country treat business websites as covered by Title III of the Americans with Disabilities Act, and there is no small-business exemption. More than 5,000 digital-accessibility lawsuits were filed in 2025 — up roughly 20% over 2024 — and a large share of them named small and mid-sized companies. A small business ADA website lawsuit usually starts with a demand letter rather than a courtroom, but the financial exposure is real either way.
Here is what the law actually says, why small companies get targeted, what a case typically costs, and the steps that genuinely reduce your risk.
Why are small businesses targets for ADA website lawsuits?
Because they settle. Defending a federal lawsuit costs more than settling one, and plaintiff-side firms know a small retailer will do the math and write a check. Filing at volume against smaller defendants is a business model, not an anomaly.
The targeting is also easy. The 2025 WebAIM Million report found detectable WCAG failures on 94.8% of the top one million homepages — most commonly low-contrast text, missing image alt text, missing form labels, and empty links or buttons. Those same failures show up in automated scans in seconds, which is exactly how serial plaintiffs build their filing lists. We break down the selection process in how ADA serial plaintiffs pick their targets.
The industry pattern is consistent: roughly 70% of web-accessibility suits hit e-commerce sites, about 18% target food service, and around 4% healthcare, with the rest spread across fitness, education, travel, and entertainment. If you sell anything online, you are in the most-sued category.
What law says my website has to be accessible?
Title III of the ADA requires places of public accommodation to be accessible to people with disabilities. There is no formal federal regulation naming a technical standard for private-sector websites — but the Department of Justice has long taken the position that business websites are covered, and most courts agree. In practice, courts and settlement agreements point to the Web Content Accessibility Guidelines (WCAG), almost always at Level AA, as the benchmark.
The case law backs this up. In Robles v. Domino's Pizza (9th Cir. 2019), the court held the ADA applies to a website and app connected to physical locations — and the Supreme Court declined to review the decision. National Federation of the Blind v. Target, the early landmark, settled in 2008 with a $6 million class fund plus remediation. One appellate decision, Gil v. Winn-Dixie (11th Cir. 2021), briefly went the other way before being vacated, so the circuit split remains unresolved. Unresolved does not mean safe: plaintiffs simply file where the law favors them.
State laws raise the stakes
California's 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 — which is why California demand letters are so common. New York layers state and city human-rights laws on top of the ADA and leads the nation in state-court web-accessibility filings, while Florida is the most active state for federal filings.
One more signal of where things are headed: in April 2024 the DOJ finalized a rule requiring state and local government websites to meet WCAG 2.1 AA, with compliance deadlines now running to April 2027 and April 2028 after a 2026 extension. It does not bind private businesses, but it shows which direction regulation is moving.
What does a small business ADA website lawsuit cost?
Most cases settle for between $10,000 and $75,000, plus a commitment to remediate the site. The average settlement runs $30,000 or more — and that figure does not include your own attorney's fees. Add the remediation work itself, which you would have needed anyway, and the lawsuit is pure overhead stacked on top of the fix. We break the numbers down further in what an ADA website lawsuit actually costs.
The cheapest version of this problem is the one where you fix the site before anyone files.
Won't an accessibility widget protect me?
An overlay will not protect you, and the record on this is now unambiguous. In January 2025 the FTC announced a $1 million action against accessiBe, alleging the company deceptively claimed its widget could make any website WCAG-compliant; the final order, approved in April 2025, bars unsubstantiated compliance claims. The National Federation of the Blind formally opposes overlay products, describing them as "not only ineffective but harmful." And UsableNet's reports repeatedly find that hundreds of companies sued each year already had a widget or overlay installed when the lawsuit arrived.
One distinction matters here. A preference widget — user-facing display settings like contrast and text size, added to a site that is already accessible at the code level and making no compliance claims — is a legitimate convenience feature; our own site runs one. A "compliance" overlay is a different product: a third-party script sold as making a broken site compliant, a claim no script can substantiate. The problem is the claim, not the button. More in why overlay widgets fail.
What should a small business do right now?
- Find out where you stand. Start with a scan, but know its limits: automated tools can detect only roughly a third of WCAG success criteria. Our free accessibility audit pairs automated scanning with expert human review, so you see the whole picture rather than the machine-readable slice of it.
- Fix the high-frequency failures first. Low-contrast text, missing alt text, unlabeled form fields, and empty links or buttons are the most common detectable failures on the web — and the first things a plaintiff's expert will screenshot.
- Benchmark against WCAG 2.2 AA. WCAG 2.2 has been the current W3C Recommendation since October 2023, and Level AA is the level courts, regulators, and settlement agreements consistently reference.
- Keep it fixed. Sites regress with every redesign, plugin update, and content upload. Ongoing monitoring catches new issues before a scanner-armed plaintiff does.
Frequently asked questions
How likely is it that my small business actually gets sued?
No honest firm will quote you odds. What the data shows: 8,667 ADA Title III lawsuits were filed in 2025 — among the highest years on record — and more than 5,000 of them targeted websites and apps. Risk concentrates in e-commerce and food service, and in businesses reachable from New York, Florida, and California. And because over 1 in 4 U.S. adults live with a disability, an inaccessible checkout flow gets encountered constantly — by potential customers as well as potential plaintiffs.
Is there a law that specifically requires WCAG for my website?
Not for private businesses — no federal regulation names a technical standard under Title III. But WCAG at Level AA is the de facto benchmark courts, the DOJ, and settlements reference, and the DOJ's 2024 rule for state and local governments formally adopted WCAG 2.1 AA. If you sell to EU consumers, the European Accessibility Act — enforced since June 2025 — explicitly covers e-commerce as well. Practically speaking, WCAG 2.2 AA is the standard to build to.
What should I do if I've already received a demand letter?
Don't ignore it, and don't panic-install an overlay — both make things worse. Talk to a lawyer, preserve the letter and the current state of your site for documentation, and start genuine remediation immediately; a credible fix already underway changes the negotiation. We've published a step-by-step guide on what to do when you get an ADA website demand letter.
Not sure whether your site would survive a plaintiff's scan? Request a free accessibility audit from ADA Fail — automated scanning plus expert human review, with a plain-English report on exactly what to fix and in what order. It costs nothing to find out where you stand.