There is no small business exemption in the ADA, and a one-line accessibility widget will not protect you: 134 of the 432 businesses sued over website accessibility in August 2026 already had a third-party widget installed. Real risk reduction comes from fixing the specific WCAG failures that show up on 95.9% of home pages, starting with the handful that account for almost all of them.
Suvysoft builds and audits small business websites, and the accessibility question comes up in nearly every one of those conversations now, usually after a demand letter or a scare from a competitor's lawsuit. The legal exposure is real, but most of what gets sold to fix it, an overlay widget, a vague "compliance" badge, does not hold up. This is what actually moves the needle.
Does the ADA really apply to a small business website?
Yes. Title III of the ADA requires that businesses open to the public provide "full and equal enjoyment" of their goods and services to people with disabilities, and the Department of Justice's own guidance confirms this covers websites, with no revenue or headcount threshold that exempts a smaller company. (ADA.gov)
The Department of Justice has never issued a formal regulation spelling out exactly what "accessible" means for a private business site. Its guidance points businesses toward the Web Content Accessibility Guidelines instead, and courts deciding real cases have converged on WCAG 2.1 Level AA as the practical bar. That gap between "no formal regulation" and "an actual bar courts use anyway" is exactly why lawsuits keep climbing: there is no compliance certificate to hold up in court, only evidence that the site actually works for a disabled visitor.
How many businesses actually get sued over this?
Plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024, according to Seyfarth Shaw's ADA Title III tracker. Halfway into 2026, the same tracker counted 5,006 federal ADA Title III suits filed, putting the year on pace to clear 10,000 for the first time since 2021. (Seyfarth Shaw)
Companies under $25 million in annual revenue made up 64% of defendants in the first half of 2025, according to UsableNet's own lawsuit tracker, which monitors filings directly in federal and New York and California state courts. Retail, restaurants, travel, healthcare, and financial services see the heaviest volume, but the pattern that matters for a small business is simpler: a small group of law firms files most of these suits, and they target sites with obvious, reproducible, easy-to-screenshot barriers, not sites that happen to be big. (UsableNet)
Does installing an accessibility overlay actually protect you?
No, and the evidence on this got a lot more concrete in 2025 and 2026. UsableNet's tracker found that 134 of the 432 businesses sued in August 2026, about 31%, already had a third-party accessibility widget installed when the suit was filed. Across all of 2025, the firm reported that 28% of lawsuits specifically cited an overlay as part of the barrier, not the fix.
The regulatory record backs this up. In April 2025, the Federal Trade Commission finalized a $1 million order against accessiBe, one of the largest overlay vendors, for falsely claiming its widget could make "any website" WCAG-compliant. The FTC's complaint quoted the company's own marketing: that installing "one line of code" made a site compliant with 30% of WCAG's requirements immediately and the remaining 70% within 48 hours through an automated process. The final order bars the company from making that kind of claim again for 20 years unless it can back it up with evidence. (FTC)
The technical reason overlays fall short is straightforward: screen readers like JAWS, NVDA, and VoiceOver read the underlying HTML, not an overlay script layered on top of it. An overlay can adjust font size or contrast toggles, but it cannot rewrite a page's actual heading structure, fix a missing form label, or add keyboard support to a custom dropdown. It changes what a sighted user sees on the surface, not what an assistive technology user's tools actually parse underneath.
What actually causes most of the risk, and what does it cost to fix?
This is the part that gets buried under lawsuit statistics: most of the risk sits in a short list of specific, fixable problems, not a sprawling, expensive rebuild. WebAIM's 2026 analysis of one million home pages found that 95.9% had at least one detected WCAG failure, averaging 56.1 errors per page, but 96% of all errors detected across the entire sample fell into just six categories. (WebAIM)
| Failure type | Share of home pages affected | Typical fix |
|---|---|---|
| Low contrast text | 83.9% | CSS color adjustment, no rebuild |
| Missing image alt text | 53.1% | Content-level fix, no developer required |
| Missing form input labels | 51.0% | Template or component fix |
| Empty links (no text or label) | 46.3% | Add link text or aria-label |
| Empty buttons | 30.6% | Add button text or aria-label |
| Missing page language attribute | 13.5% | One HTML attribute, site-wide |
None of the top three require custom development work. Low contrast text is a color value change, missing alt text is a content edit, and missing form labels are usually a template-level fix that applies across every page built from the same form component at once. A site that only fixed these six categories would resolve the overwhelming majority of what shows up in an actual scan, which is a different, cheaper project than the full manual audit a demand letter eventually forces.
Real-world pricing reflects that split. A full professional audit against WCAG 2.1 AA, plus remediation and a validation pass, typically runs $1,500 to $7,500 depending on page count and how much custom interactive functionality is in scope. A hybrid approach, an automated scan plus in-house fixes for the content-level issues above and a developer only for the harder interactive components, commonly lands in the $500 to $3,000 range for a typical small business site. Waiting for a demand letter costs more either way: most settle in the $5,000 to $50,000 range before a case is even filed, and a case that reaches active litigation commonly settles for $30,000 to $150,000 or higher.
What should you fix first if you cannot do it all at once?
Work down from the highest-frequency, lowest-cost items first, since that order clears the most real risk per hour spent.
- Choose manual remediation when the issue is contrast, alt text, form labels, or link and button text, since these are inexpensive, do not touch site logic, and directly address the six categories behind 96% of detected errors.
- Choose a developer for custom widgets, interactive components (menus, sliders, modals, date pickers), and anything requiring keyboard focus management, since these need code changes an overlay cannot make and a content editor cannot fix alone.
- Never rely on an overlay alone to close out a demand letter or satisfy a compliance question from a partner or investor, since it does not touch the underlying HTML a screen reader actually reads, and it now shows up in about three of every ten new lawsuits as a documented part of the plaintiff's evidence.
Does fixing this also help with anything besides lawsuit risk?
Yes. The same fixes that reduce legal exposure, clean heading structure, labeled form fields, sufficient contrast, descriptive link text, also improve how search engines and AI answer engines parse a page, since both rely on the same underlying structure a screen reader does. That overlap is one reason accessibility work folds naturally into the same engagement as SEO and general site quality work rather than sitting off to the side as a separate compliance project.
Suvysoft treats WCAG 2.1 AA as a build requirement, not an add-on, on every web development engagement, testing contrast, labels, and keyboard behavior on the actual live page before launch instead of relying on an automated scanner or a vendor's badge. That is a narrower but related question than the one we cover in our piece on AI chatbot accessibility: a chat widget has its own keyboard and screen reader requirements on top of whatever the rest of the site needs. We also look at the mobile-usability side of the same standard, including tap target sizing, in our post on responsive web design.
Frequently asked questions
Is website accessibility legally required for a small business?
Yes. Title III of the ADA applies to any business open to the public, with no size or revenue exemption, and the Department of Justice's own guidance confirms it covers websites. There is no formal federal regulation naming a specific technical standard, but courts consistently use WCAG 2.1 Level AA as the practical benchmark, and plaintiffs' firms file against small businesses at least as often as large ones: companies under $25 million in revenue made up 64% of defendants in the first half of 2025.
Will an accessibility overlay widget protect my business from a lawsuit?
Not reliably. UsableNet's tracker found that about 31% of businesses sued in August 2026 already had a third-party accessibility widget installed, and 28% of all 2025 lawsuits specifically cited an overlay as part of the problem. The FTC also fined the overlay vendor accessiBe $1 million in 2025 for falsely claiming its product could make any site fully WCAG-compliant, which is a strong signal that the marketing behind these tools has outpaced what they can actually deliver.
What is the single biggest accessibility problem on most websites?
Low contrast text, found on 83.9% of the one million home pages WebAIM analyzed in its 2026 report. It is also one of the cheapest problems to fix, since it is usually a CSS color value change rather than a structural or code-level rebuild.
How much does it cost to make a small business website ADA compliant?
A full professional audit, remediation, and validation typically runs $1,500 to $7,500. A hybrid approach using an automated scan plus in-house fixes for content-level issues (contrast, alt text, form labels) and a developer only for complex interactive components commonly runs $500 to $3,000 for a typical small business site. Waiting for a demand letter is more expensive either way: most pre-lawsuit settlements land between $5,000 and $50,000.
What happens after someone sends a demand letter about my website?
Most cases never reach a courtroom. A demand letter typically lists specific, reproducible barriers, often generated from an automated or manual audit, and the business has the option to negotiate a settlement and fix the site rather than litigate. Settling before a lawsuit is filed generally costs less than settling after one is, and litigated cases can run into six figures, so the fastest way to reduce cost is fixing the highest-frequency issues before a letter ever arrives.
Do I need a full accessibility audit, or can I fix the basics myself?
You can meaningfully reduce risk without a full audit by addressing the six failure types that account for 96% of all detected errors: contrast, alt text, form labels, empty links, empty buttons, and a missing page-language attribute. A full manual audit still matters for interactive components like menus, sliders, and custom form widgets, since those require testing an automated scanner cannot fully perform on its own.
Not sure where your site actually stands? Talk to us about a straightforward review before a demand letter forces the question.