Does your small business website need to be ADA compliant?
Nearly 5,000 web accessibility lawsuits were filed in 2025, most against smaller companies — and about a quarter of the defendants had already installed an accessibility widget. What ADA compliance actually requires, from a builder, not a lawyer.
Short answer: yes, treat it as if it does. Title III of the Americans with Disabilities Act prohibits discrimination in places of public accommodation, courts have repeatedly treated business websites as such places, and the Department of Justice has published guidance saying plainly that the ADA applies to web content. There is no small-business exemption you can point to, and the businesses being sued are not the Fortune 500. Before going further: I am not a lawyer and this is not legal advice — it is a builder's description of the standard courts use and what meeting it looks like in practice.
The numbers, without the panic
UsableNet, which tracks these cases, counted nearly 5,000 web accessibility lawsuits filed in 2025, and its reporting through the year found that roughly two-thirds of defendants were companies with under $50 million in annual revenue — heavily weighted toward e-commerce and retail sites run on ordinary small-business platforms. The suits cluster in a handful of plaintiff-friendly states, but demand letters are cheaper than lawsuits and travel everywhere. The honest framing for a South Carolina or North Carolina business is not that a lawsuit is likely this year; it is that the exposure is real, the settlement demands land in the thousands, and the fix costs less than the risk.
What "compliant" actually means
The ADA itself contains no technical checklist for private business websites. In practice, courts and the DOJ point to the Web Content Accessibility Guidelines — WCAG — at Level AA as the reference standard, which is why every serious accessibility conversation ends up there. I have written a separate piece on what WCAG actually requires; the short version is that most failures on small business sites are ordinary construction defects: images without alt text, text without enough contrast, forms whose fields a screen reader cannot name, pages that cannot be navigated by keyboard. Built correctly from the start, none of these cost extra. Retrofitted after a demand letter, all of them do.
The widget shortcut that isn't one
There is an industry selling overlay widgets — a script you paste into your site that promises automated compliance. The 2025 numbers are the clearest argument against them: EcomBack's annual tally found 983 lawsuits that year, about a quarter of the total, filed against websites that already had an accessibility widget installed. A script layered on top of a page cannot repair what is wrong in the page's own structure, and plaintiffs' firms know it — some filings now cite the widget itself. If a vendor tells you a monthly subscription makes the problem go away, the data says otherwise.
About a quarter of the businesses sued in 2025 already had an accessibility widget installed. Compliance lives in how the site is built, not in a script pasted over it.
What building for it looks like
Every site I build is checked against WCAG 2.1 AA with axe-core — the same engine behind the accessibility audits in Chrome's own developer tools — and ships with zero critical and zero serious violations, verified, not asserted. Automated checks catch only part of the standard, so keyboard navigation and screen-reader behavior get checked by hand. And because accessibility is a property of the whole build rather than a feature bolted on, the same work makes the site faster and easier for search engines to read. If you already have a website and want to know where it stands, the free audit runs exactly these checks and hands you the results — including the specific violations a demand letter would cite — whether or not you ever hire me.