Does My Small Business Website Have to Be ADA-Compliant?

UsableNet’s 2025 year-end report counted 5,114 digital accessibility lawsuits filed against businesses across federal and state courts — roughly 3,195 in federal court and 1,919 in the New York and California state systems. Nearly half of the federal filings named a defendant that had already been sued once. eCommerce accounted for about 70% of filings and food service 21%; most of the rest were local service businesses.

The uncomfortable part is that there is no single federal rule you can point to and say, “our site meets that, we’re done.”

Where the law actually stands

Title III of the Americans with Disabilities Act applies to “places of public accommodation.” Congress did not define that to include websites in 1990, because there weren’t any, and Congress has not amended the definition since. Courts have filled the gap the usual way, unevenly: the Ninth Circuit and much of the country treat a business’s website as part of the public accommodation, especially when it ties to a physical location; the Eleventh Circuit has been more skeptical. The practical effect is that if you sell to or serve the general public, your website is treated as covered, and the argument that it isn’t is not one you want to be paying a lawyer to make.

There is also no federal regulation telling you exactly what “accessible” means for a business site. The Department of Justice’s Title II rule, published in April 2024, requires WCAG 2.1 Level AA for the websites of state and local governments. It does not apply to private business. But courts and settlements have effectively adopted WCAG 2.1 Level AA as the benchmark for private sites too, because it is the only widely accepted standard anyone is measuring against.

So the working answer is: yes, in practice, and the yardstick is WCAG 2.1 Level AA, and the enforcement mechanism is a demand letter from a plaintiff’s firm rather than a government inspection.

Who is being sued, and why the pattern matters

UsableNet’s data is worth reading with a small-business eye rather than an industry-analyst one. In the first half of 2025, roughly 36% of defendants had annual revenue above $25 million. Most defendants were smaller than that. If you run a Springfield print shop or a Jefferson City medical spa with an online booking form, you are the majority of who this is happening to.

Two things drive the pattern. First, the filings are done at scale by a small number of firms, using accessibility scans to identify sites with machine-detectable failures and then sending template demand letters. Second, small business sites are more likely to have those failures unfixed. Plaintiff firms look for a shopping cart, an appointment form, or a menu that a screen reader cannot use. The size of the company behind that page is secondary.

What the Graves bill would change, and where it stands

In February 2026, Rep. Sam Graves, whose district covers northern Missouri, introduced H.R. 7328, the Protecting Small Businesses from Predatory Website Lawsuits Act. It would amend Title III so that a civil lawsuit over a website could not be filed until the owner has been given written notice of the specific failures and 180 days to fix them.

The House passed it on April 14, 2026, on a suspension vote of 396 to 10. That is a lopsided margin. It has not passed the Senate, so it is not law, and until it is, the current pattern continues. But the signal from that vote is that the notice-and-cure framing is where this eventually lands.

That matters for planning. If you have real accessibility issues today, the future version of the world still expects you to fix them. It just gives you a defined runway to do it in.

Overlay widgets are not the answer

There is a well-funded category of products that install a JavaScript widget on your site and promise to make it accessible at runtime. If a vendor is pitching you a monthly subscription for a floating icon in your bottom-right corner, that is what they are selling.

Independent testing has been consistent about this for years. The National Federation of the Blind has issued formal statements naming several overlay vendors and saying the tools do not reliably resolve WCAG failures; Deque Systems, a firm that has been in accessibility engineering longer than most of these vendors have existed, has published detailed analyses reaching the same conclusion. Users of assistive technology report that overlays interfere with the screen readers and keyboard shortcuts they already have configured.

Plaintiff firms know this too, and have filed suit against sites carrying overlays. Buying one has not proved to be a defense.

What actually reduces risk

None of this is glamorous, which is roughly why it works.

Fix the code, not the surface. The WebAIM Million report, which analyzes the top million home pages every year, has found that the same handful of failures account for the overwhelming majority of what a scan detects: low-contrast text, missing image alt text, missing form labels, empty links, and empty buttons. Fixing those in the underlying markup gets you past the machine-detectable filter that most demand letters are built on.

Prioritize the pages that carry a transaction. A checkout, a contact form, a booking or appointment page, or an online menu are the pages courts most consistently treat as core to a public accommodation. An unusable homepage is a problem. An unusable checkout is a lawsuit.

Have real people test it. A scan will catch the technical failures; a keyboard-only test of your own booking flow will catch the practical ones. If you cannot complete your primary customer action without using a mouse, neither can a real user of assistive technology.

Write down what you did, and when. That record of ongoing accessibility work is the kind of thing a competent lawyer can use to reduce a settlement. It is also what the Graves bill, if it passes, would formalize into the 180-day cure window.

Put it into normal quality assurance. Accessibility drifts. New pages get built, plugins get updated, an image gets swapped, and old issues come back. Rolling accessibility checks into your normal update process is the difference between staying past the machine-scan threshold and slipping back into it.

If you are a church reading this, our earlier note on the religious exemption from Title III is the direct answer to your version of this question. If you run a business with an ongoing site care plan, this kind of maintenance is what your hosting and support work should already be catching, and if it is not, that is worth asking about.

The short version: the law is fuzzier than the volume of lawsuits suggests, the standard everyone uses is WCAG 2.1 Level AA, no widget will do the work for you, and the fix is the ordinary kind of website hygiene most sites have been putting off.