What ADA accessibility lawsuits actually target on a small-business website

A client called us in March worried about a demand letter, not a redesign. Their site looked fine, ranked fine, and converted fine — and none of that mattered, because the checkout flow couldn't be navigated with a keyboard. That call is becoming routine. According to UsableNet's 2025 Digital Accessibility Lawsuit Report, plaintiffs filed 3,117 website accessibility lawsuits in U.S. federal court in 2025, up 27% from 2,452 cases in 2024. This isn't a niche legal curiosity anymore — it's a real line item on the risk list for any small business with a website.

E-commerce is the target, not the exception

The same UsableNet report puts e-commerce at roughly 69% of all 2025 digital accessibility filings. That tracks with what we see in client audits: the sites most exposed are the ones with product listings, cart flows, and checkout forms — exactly the pages a business can least afford to have blocked for anyone. Settlement figures we've seen referenced in legal coverage of these cases typically land between $5,000 and $75,000 before attorney fees, which is a rough way to fund a fix you could have made proactively for a fraction of that.

An accessibility widget is not a fix

The instinct to bolt on an "ADA compliance" overlay widget is understandable and, based on the data, doesn't hold up. UsableNet found that 22.64% of 2025 lawsuits — 456 of them — were filed against sites that already had an accessibility widget installed. The FTC reinforced that this year too, reaching a $1 million settlement with overlay provider accessiBe after finding the company had marketed its product as guaranteeing ADA compliance when it left real barriers in place. Widgets can adjust font size and contrast on the surface; they generally can't fix a checkout form with no labels or a modal that traps keyboard focus, which is where the actual lawsuits originate.

There is a real standard, even without a small-business-specific law

Title III of the ADA, which covers private businesses, still doesn't name a technical standard in the statute itself — but courts and settlements have converged on one anyway. The Department of Justice's April 24, 2024 final rule for Title II formally adopted Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the required technical standard for state and local government sites. It doesn't legally bind private businesses, but it's the same benchmark most Title III consent decrees and demand-letter settlements now reference. If you're going to build to a standard, WCAG 2.1 AA is the one that shows up in front of a judge.

The checks that actually move the needle

We added a dedicated accessibility pass to our own pre-launch checklist for exactly this reason, and most of it isn't exotic:

• Every image gets real alt text — not the filename, not left blank, not "image123.jpg."
• Every form field has a linked label, and error messages are announced, not just colored red.
• Keyboard-only navigation works end to end, including modals, dropdown menus, and the checkout flow — tab through it with the mouse unplugged.
• Color contrast meets 4.5:1 for body text against its background, checked with a tool, not by eye.
• Focus states are visible on every interactive element, so a keyboard or switch-device user can see where they are on the page.

None of these require a plugin or a monthly subscription — they're fixes made once, directly in the markup, the same way we already check performance scores in Lighthouse's Accessibility category during every speed audit we run.

If you haven't had anyone actually tab through your own checkout with a keyboard, that's worth twenty minutes this week. If it fails, our web design and build service treats an accessibility pass as a standard part of any rebuild, not an add-on billed separately after the fact.