Is your website an ADA lawsuit risk? What US small businesses need to know

Most American small business owners first hear about web accessibility when a demand letter arrives. By then the conversation is about settlement rather than compliance, and it is considerably more expensive.

Here is the actual risk picture, based on litigation data rather than the fear marketing that surrounds this topic.

How big is the risk, really?

Plaintiffs have filed more than 4,000 digital accessibility lawsuits every year since 2021, and over 25,000 between 2018 and 2025. In 2025 alone, federal filings reached 3,117 — up 27% on the year before — with state court cases on top of that.

The two things that surprise business owners:

• It is not only large companies. In the first half of 2026, businesses under $50 million in revenue were still 68% of targets.
• Filings are concentrated. In Q1 2026, ten law firms accounted for 82.5% of all filings. This is a small number of practices operating at volume, not a broad wave of individual complaints.

Which industries get targeted?

Industry	Share of Q1 2026 filings
Restaurants, food and beverage	32.2%
Lifestyle, fashion and apparel	25.2%
All other industries combined	42.6%

Restaurants moving into first place is recent — fashion led in Q1 2025. If you run a restaurant with online ordering, you are currently in the single most targeted category in the country.

Which platforms get targeted?

Platform	Share of Q1 2026 filings
Shopify	44.3%
Custom-coded sites	31.2%
WordPress	14.5%

Shopify's share reflects how many small e-commerce businesses are on it rather than a flaw in the platform. A default Shopify theme is not accessible out of the box, and most store owners assume it is.

Which states?

Filings concentrate heavily. In January 2026: Florida led with 88, California 62, New York and Illinois 60 each, Pennsylvania 21. Illinois has been climbing fast and took first place in February 2026 — a shift worth noting if you assumed this was a New York and California problem.

The widget question

This is the most expensive misunderstanding in the field.

Accessibility overlay widgets — the small icon that opens a panel of contrast and font-size controls — are sold as a compliance solution. The litigation data does not support that claim. In Q1 2026, 25.5% of lawsuits were filed against sites that were already running an accessibility widget. Lawsuits against widget-using companies were recorded in every single month of the first half of 2026.

A widget can help some users with some tasks. It does not fix the underlying markup, and the underlying markup is what a plaintiff's expert examines. Treating one as insurance is how businesses end up paying twice — once for the subscription and once for the settlement.

What does the ADA actually require for websites?

The ADA itself predates the modern web and does not name a technical standard for private business sites. Courts have generally treated WCAG 2.1 Level AA as the working benchmark, and settlement agreements routinely specify it.

For public entities the picture is now explicit: a DOJ rule requires WCAG 2.1 AA for state and local government, with large entities due by April 2027 and smaller ones by April 2028 after an interim extension. Private businesses are not bound by that timetable, but it establishes WCAG 2.1 AA as the accepted federal reference point.

The eight barriers that appear in nearly every complaint

1. Images without alt text. Product photos especially — a screen reader user cannot tell what is for sale.
2. Poor color contrast. Light gray text on white is the most common single failure.
3. Forms without labels. A placeholder inside the box is not a label.
4. Keyboard traps. Focus enters a menu or modal and cannot get out.
5. Checkout that cannot be completed without a mouse. The most damaging one on an e-commerce site.
6. Missing focus indicators. Designers remove the outline because it looks untidy; keyboard users then cannot see where they are.
7. Video without captions.
8. No accessibility statement. Its absence is conspicuous and it is trivially easy to add.

How to check your own site in twenty minutes

1. Run Lighthouse. Built into Chrome — open DevTools, Lighthouse tab, run the Accessibility audit. It catches contrast, missing labels and missing alt text automatically.
2. Unplug your mouse. Navigate homepage to product to checkout, or homepage to contact form to submit, using only Tab, Shift+Tab and Enter. Note every point where you get stuck or lose track of where you are.
3. Turn on a screen reader. VoiceOver on Mac is Cmd+F5; Narrator on Windows is Ctrl+Win+Enter. Listen to your homepage for two minutes. It is uncomfortable and it is instructive.
4. Zoom to 200%. Does the layout hold, or does content overlap and disappear?

An automated tool catches roughly a third of issues. The keyboard test catches most of the rest. Neither replaces a manual audit, but together they find what plaintiffs' firms typically cite.

What to do if a demand letter arrives

• Do not ignore it. These firms file at volume and follow through.
• Talk to an attorney who has handled ADA Title III matters specifically.
• Start remediating immediately. Documented, dated progress materially changes the negotiation.
• Do not install a widget and claim compliance. Opposing counsel is familiar with them and a quarter of filings already involve sites running one.
• Keep records of the audit, the fixes, and the dates.

The honest cost comparison

Path	Typical cost
Building accessibility in during a new site	Little to no premium if specified up front
Remediating an existing site	$2,000 – $15,000 depending on size
Widget subscription	$500 – $6,000/year, and does not prevent filings
Settling a lawsuit	Commonly five figures, plus remediation you still have to do

The pattern is consistent: doing it during a build costs almost nothing extra, doing it later costs real money, and doing it after a filing costs the most and buys you nothing you would not otherwise have had.

We specify WCAG 2.1 AA on every build as standard rather than as an add-on, for the straightforward reason that retrofitting is several times more expensive than getting it right the first time. If you are commissioning a site, put that standard in the scope document — and if the developer is unsure what it means, that is useful information before you have paid anything.