ADA Website Compliance Lawsuits 2026: A Legal Protection Guide for Small Businesses

What the risk actually is, and what it isn't

The accessibility lawsuit conversation tends to oscillate between two unhelpful extremes: "nobody gets sued over a website" and "one missing alt tag will cost you 50,000 dollars".

Neither is accurate, and the gap between them is where a small business has to make decisions. So this is an attempt at the plain version, with the caveats up front.

This is not legal advice. Accessibility law varies by country, state, and business type, and it changes. If you're facing a demand letter, or you're in a regulated sector, talk to a lawyer who does this work. What follows is a description of the landscape and the practical measures that reduce risk regardless of how the law develops.

The American picture, precisely

The ADA is the statute people mean when they talk about US website compliance, and the detail matters more than the headlines.

Title III covers businesses open to the public: shops, restaurants, clinics, hotels, law firms. It says places of public accommodation must not discriminate on the basis of disability. It does not mention websites, and here is the thing almost every article skips: there is still no federal regulation specifying a technical standard for private-sector websites.

That means courts have had to decide, case by case, whether a website is covered and what "accessible" requires. The results have been inconsistent. Some circuits have found that a website isn't a place of public accommodation at all. Others have allowed claims to proceed. Several notable cases ended in settlements or were dismissed as moot after the site was fixed, so they set no lasting precedent.

What has filled the vacuum is WCAG, the Web Content Accessibility Guidelines. It isn't written into Title III by regulation, but it's the benchmark that appears in consent decrees and settlement agreements, and it's the standard plaintiffs cite. Practically, WCAG 2.1 Level AA is what "accessible" has come to mean in this context, with WCAG 2.2 increasingly referenced since it became a W3C recommendation in 2023.

Title II is different and worth knowing about. It covers state and local government entities, and there is now an actual regulation: the Department of Justice's 2024 rule requiring WCAG 2.1 AA for public entities, with compliance dates falling in 2026 and 2027 depending on population size. If you work with or for a public body, that rule is concrete and dated. If you're a private business, it doesn't apply to you directly, but it does mean the public sector will increasingly expect accessible documents and accessible vendor platforms.

The state and provincial layer

Federal law is only part of it.

California has the Unruh Civil Rights Act, which provides statutory damages per offence and has generated a large volume of website claims, often in state court where filing is cheap.

New York has seen a concentration of federal filings, and Florida has an active plaintiff bar.

Beyond the US: Ontario's AODA imposes accessibility requirements on organisations above a size threshold, and the European Accessibility Act applies to a defined list of consumer-facing products and services, with obligations phasing in from 2025. If you sell into Europe, that's a distinct regime from the ADA.

What actually drives the lawsuits

The pattern is well documented, and it's less about justice in individual cases than about volume.

A small number of firms and repeat plaintiffs scan websites with automated tools, identify barriers, and send demand letters or file. Automated scanning can detect a specific class of problems: missing alternative text, insufficient contrast, unlabelled form fields, missing document language, empty links and buttons. It cannot detect whether a flow is usable, whether focus is trapped in a modal, or whether a screen reader can complete a checkout.

Which means the typical suit is filed over the detectable things, and the remedies demanded usually include an audit, remediation to WCAG 2.1 AA, and a monitoring period.

The reports from firms that track filings have shown roughly several thousand federal website accessibility suits a year in the US in recent years, with state-court filings on top. The exact count by year is worth checking against a current tracker rather than trusting any single number in an article, including this one.

Two patterns are consistent: small and mid-sized businesses are heavily represented, and e-commerce and service businesses with online booking or payment flows are the most frequent targets, because a barrier there is a barrier to a transaction.

What reduces risk, in order of usefulness

1. Fix real barriers on your highest-value flows

Not the whole site at once. The pages where someone books, buys, enquires, or pays.

That means: keyboard operability end to end, visible focus, labelled form fields, readable contrast, alt text on meaningful images, captions on video, and no flow that depends on a drag gesture.

The reason to start there isn't legal strategy, it's that a barrier in the booking flow is the one that gets noticed and the one that costs you money.

2. Document what you did

If a claim arrives, the difference between an unhelpful conversation and a defensible one is evidence of a genuine programme: an audit report with dates, a prioritised remediation list, tickets closed, a stated standard (WCAG 2.1 AA), and a named person responsible.

Documented effort has repeatedly mattered more than the absence of every possible defect, because full conformance on a real site is a moving target.

3. Publish an accessibility statement

One page: your target standard, known limitations with dates, how to report a problem, and a contact route that gets a reply. It's not a shield, but it's the difference between "they never thought about this" and "they're working on it", and it gives a person an alternative to complaining to a lawyer.

4. Don't buy an overlay and call it done

Accessibility overlay widgets promise automated compliance from a script tag. They are widely criticised by accessibility practitioners because they don't fix underlying code, they can conflict with a user's own assistive technology, and some have been found to introduce new problems.

There's now a regulatory dimension too: the US Federal Trade Commission fined accessiBe one million dollars in early 2025 over deceptive claims that its automated widget could make a site WCAG compliant, including claims in customer testimonials. Treat "AI makes you compliant" as a marketing claim, not a technical one.

An overlay may buy a claim of effort. It does not produce accessibility.

5. Put it in contracts

If an agency builds or maintains your site, the contract should state the accessibility standard, who tests it, and what happens when defects are found. If you buy a booking platform or a storefront, ask for an Accessibility Conformance Report (a VPAT) and check whether the vendor's roadmap addresses gaps.

Most small businesses inherit their accessibility problems from a vendor. Contract language is how that becomes someone's job.

6. Check your insurance

Some general liability and cyber policies exclude or sub-limit accessibility claims; some offer coverage for them. Worth a question to a broker, before anything happens.

What doesn't help

• Ignoring it because you're small. Volume filings target small businesses precisely because they settle.
• Chasing a 100 percent score from an automated scanner. It's a partial measure, and it produces effort in the wrong places.
• Fixing a complaint quietly and hoping. Remediation helps; the absence of a programme is what makes the next claim easier.
• Removing features instead of making them accessible. Cutting the booking form doesn't reduce exposure, it removes revenue.

Where to start

Pick your booking or contact flow and try to complete it with a keyboard only, then with a screen reader on a phone. Write down what breaks, fix the worst three, and date the list. That's the beginning of a programme, and the programme is the thing that matters.

A free digital presence audit on Webcheckhub includes accessibility basics within website health, which tells you whether the detectable problems are widespread or concentrated. When you want a documented audit against WCAG 2.1 AA with remediation implemented, Solutions Elites handles accessibility work for small businesses.