Does My Small Business Website Need to Be ADA Compliant?
A letter arrives from a law firm you've never heard of. It claims your website is inaccessible to a blind or visually impaired customer and violates the Americans with Disabilities Act. It demands a payment to make the claim go away, or threatens a lawsuit if you don't respond within a set number of days. There's no warning before it lands, and nothing on your website ever told you this was a risk.
For most small businesses, the practical answer is yes: the website should meet accessibility standards, and the risk is real regardless of business size. UsableNet reviewed more than 5,000 ADA-related digital accessibility lawsuits filed in 2025, and e-commerce accounted for 69% of all digital accessibility lawsuits in 2025.
There's no single federal law spelling out exact web accessibility rules for private businesses the way there is for building entrances or parking spaces. That gap is precisely why this issue catches small business owners off guard.
Why There's No Official Rulebook, But Still Real Risk
The ADA was written in 1990, before the commercial web existed. It requires "places of public accommodation" to be accessible, but it never mentions websites. Courts have spent the last two decades deciding, case by case, whether a website counts as a place of public accommodation when it's connected to a business that serves the public. Most courts that have ruled on it say yes, especially when the site handles bookings, orders, or account access tied to a real-world business.
Without a rule written into the ADA itself, courts and plaintiffs have settled on a private technical standard as the practical benchmark: the Web Content Accessibility Guidelines, specifically WCAG 2.1 at the AA level. It's not law in the same sense as a building code, but it's what judges, settlement agreements, and plaintiff's attorneys point to when arguing a site fails to provide "meaningful access."
The recent federal rule, requiring state and local government websites to adopt and implement these standards,does not apply to private businesses, and its deadlines were extended into 2027 and 2028. It does not change a private business's obligations under Title III, the part of the ADA driving the lawsuits described above, which proceeds independently of any government compliance deadline.
Why Small Sites Get Targeted, Not Just Big Brands
This does not only happen to large retailers with legal teams and deep pockets. Small businesses are vulnerable because their sites are often built on templates, plugins and third-party themes that do not guarantee accessibility by default.
Common issues include missing image alt text, insufficient color contrast, unlabeled forms, inaccessible menus, mouse-only navigation and checkout flows that screen-reader users cannot complete. Those problems are often detectable with automated scanning tools, which allows plaintiffs' firms to identify targets at scale.
A firm doesn't need to visit your site by hand to decide whether to send a letter. Automated scanners can flag missing alt text, low-contrast buttons, or forms without labels across thousands of sites in a single sweep, and a business gets flagged the same way whether it does $50,000 a year in revenue or $50 million.
Getting sued once also doesn't clear the slate. Of the more than 5,000 digital accessibility lawsuits UsableNet tracked in 2025, a substantial share targeted companies that had already faced a prior claim, and roughly 46% of federal cases involved a repeat defendant. The pattern in that data is straightforward: a settlement, a partial fix, a new plaintiff, another filing, often within months of the first.
Why the Accessibility Widget You Bought Probably Isn't Protecting You
A lot of business owners respond to this fear by installing a plugin or overlay widget that claims to make a site ADA-compliant with one line of code. The shortcut is appealing, but the litigation data says it does not work. UsableNet's own year-end review found that an increasing number of lawsuits were filed against companies already using these tools, since widgets typically do not resolve underlying code-level accessibility issues and may interfere with assistive technologies such as screen readers. The report describes them as offering little protection against legal claims and frequently being cited as insufficient solutions.
That finding matches how these tools work. An overlay script running in the browser can adjust visual settings like font size or contrast on the fly, but it can't rebuild a checkout form that was never coded with proper labels, or fix navigation that only works with a mouse. The underlying code is still broken. A plaintiff's attorney (or their scanning tool) can usually tell the difference.
What Actually Reduces the Risk
The fix that holds up isn't a plugin, it's how the site is built. That means:
- Every image carries real alt text describing what it shows, not a filename.
- Forms, buttons, and menus have labels a screen reader can announce correctly.
- The whole site is navigable by keyboard alone, not just a mouse or touchscreen.
- Color contrast between text and background meets the WCAG 2.1 AA threshold.
- Anything interactive, like a booking calendar or checkout flow, has been tested with assistive technology, not just eyeballed.
This is a build-quality question, not an add-on question. A site built correctly from the start, or corrected by someone who understands accessible code rather than by a script bolted on afterward, holds up under scrutiny in a way a widget doesn't.
Curious where your own site stands? Our free accessibility checker scans for dozens of common WCAG issues in under 20 seconds, no signup required. It's a fast, useful first read, but confirming real ADA compliance still takes a full manual audit, not an automated scan alone.
If your site was built years ago on a template, or no one has checked it against these points, address that before a letter shows up rather than after. Our web development work builds these standards into the site itself rather than treating accessibility as something to patch on later.
Key Takeaways
- There's no ADA rule written specifically for private business websites, but courts widely treat WCAG 2.1 AA as the practical standard plaintiffs and judges point to.
- Website accessibility lawsuits are not limited to large companies; small business sites built on common templates and plugins are frequent targets because automated scanners can flag issues at scale.
- Accessibility overlay widgets have not reduced lawsuit risk according to litigation tracking data, because they don't fix the underlying code that causes the problem.
- A business that settles one accessibility claim without full remediation faces a meaningfully higher chance of being sued again.
- Real protection comes from how a site is coded, not from a bolt-on tool added after launch.
If you're not sure whether your current site would hold up to this kind of scrutiny, Mindstate Strategy can take a look. Reach out through our contact page to talk through what a properly built, accessible website involves for your business.
