Website Accessibility Lawsuits Are Surging in 2026 — What Actually Triggers One

The short version: more than 5,000 ADA website accessibility lawsuits were filed in the US in 2025, there is no small-business exemption, and a small number of law firms file the large majority of them using automated scans that don't care how big your company is. Most of what triggers a demand letter is a short, well-known list of fixable issues — low contrast text, missing alt text, unlabeled form fields — and checking for them yourself takes about two minutes. This article covers what actually happens, what it costs, and how to check.

We build Webflow sites for a living, so this is relevant to what we sell — worth saying upfront. It's also just true, and independently verifiable through the sources linked below.

The Numbers, Plainly

Reported figures vary by tracker and by how filings are counted, but the pattern across sources is consistent. Over 5,000 federal and state web accessibility lawsuits were filed in the US in 2025, with a small cluster of specialized law firms — reportedly around 16 — responsible for roughly 90% of them. Independent audits of the web's most-visited sites found detectable WCAG failures on 95.9% of the top one million homepages, averaging over 56 errors per page. Low-contrast text alone showed up on 83.9% of them.

That last number is worth sitting with. It means the odds are that your site has at least one of these issues right now, not because anyone did anything unusual, but because it is the default outcome of not checking.

How This Actually Plays Out

Understanding the mechanism removes a lot of the mystery, and most business owners never see this part explained plainly:

• A site gets scanned — usually by automated tooling that checks for the same well-documented WCAG failures at scale, across large numbers of sites, not by a person manually reviewing your business.
• A demand letter arrives, listing specific alleged violations and typically giving 20 to 30 days to respond, often with a settlement figure attached.
• The economics favor a quick settlement. These arrangements are commonly structured so the firm's fees come from the settlement itself, and the practice depends on volume and speed, not on winning any individual case at trial. That shapes the incentive on both sides: a fast, reasonable settlement is usually cheaper than fighting, and the letter is written expecting exactly that.

None of this requires malicious intent on your part, and treating it as a moral judgment about your business misses the point. It is closer to a compliance tax that most sites haven't paid yet, being collected at scale.

What Actually Gets Flagged

The failures that trigger the large majority of these letters are not exotic. They are the same handful of issues, over and over:

Notice that two of these — focus visibility and touch target size — are new requirements in WCAG 2.2, which means a site that was fully compliant with the older 2.1 standard can still fail today. Accessibility compliance is not a one-time project; the bar moves.

What The Law Actually Requires

Worth being precise here, because vague claims about "the law" are exactly what makes this topic feel scarier and more confusing than it needs to be. The ADA itself does not name WCAG explicitly. In practice, courts have consistently pointed to WCAG 2.1 Level AA as the working benchmark when deciding these cases, and WCAG 2.2 AA is now treated as current best practice by most accessibility professionals and litigators alike.

There is no small-business exemption and no revenue floor under ADA Title III. Reporting indicates the majority of these lawsuits target companies with under $25 million in annual revenue, including businesses with fewer than 15 employees. The automated scans that generate these leads do not check your headcount before flagging your homepage.

If you serve customers in the EU, the European Accessibility Act adds a parallel obligation with its own enforcement timeline — a separate legal system with the same underlying WCAG-aligned expectations, worth a quick check with counsel if that market matters to your business.

What It Actually Costs

Reported figures, again treated as ranges rather than precise numbers:

The pattern is straightforward: every dollar spent reactively, under a 20-to-30-day clock with a lawyer involved, buys far less than the same dollar spent proactively, on your own schedule, before anyone has a reason to write you a letter.

A Two-Minute Check You Can Run Right Now

No signup, no tool to install — it's already in your browser:

• Open your site in Chrome, then open DevTools (F12, or right-click → Inspect).
• Click the Lighthouse tab.
• Check only Accessibility, then click Analyze page load.

You'll get a score out of 100 and a specific, itemized list of failures — which element, which rule, why it matters — not a vague grade. This is the same category of check the automated scans behind demand letters run, so it's a genuinely honest preview of your actual exposure, not a sales pitch dressed up as a test.

Lighthouse catches a lot but not everything — keyboard-only navigation traps and focus order issues need an actual manual tab-through of your key pages (home, main service page, contact form) to catch reliably. Ten extra minutes, same session.

Why This Overlaps With Everything Else We Write About

This is not a detour from the rest of this blog — it is the same underlying skill showing up from a different angle. The semantic HTML structure that makes a page accessible is largely the same structure that helps Google rank it and helps AI assistants cite it correctly. We also found, when writing about AI-generated code's security record, that accessibility is one of the areas AI code generation reliably gets wrong — missing labels, missing alt text, insufficient contrast are exactly the same category of oversight in both contexts, because both stem from nobody having deliberately checked.

Webflow does not make a site accessible automatically — contrast choices, alt text, and form labeling are still decisions a designer has to make correctly. What it does provide is clean, controllable semantic HTML with no page-builder plugin stack fighting you, and no AI-generated markup nobody reviewed. That is a meaningfully easier starting point than either alternative, but it is a starting point, not a guarantee.

What To Actually Do About It

In order of return on effort:

• Run the Lighthouse check above on your three or four highest-traffic pages today.
• Fix contrast and missing alt text first — the two most common failures, and usually the fastest to correct.
• Manually tab through your contact form and any page with a sticky header, checking that focus is always visible.
• If you're on WCAG 2.1-level compliance already, specifically check the two new WCAG 2.2 criteria — focus visibility and 24×24px touch targets — since these are the ones a previously "compliant" site is most likely to newly fail.
• Keep a dated record of what you checked and fixed. If a letter ever does arrive, a documented, good-faith remediation history is a genuinely different conversation than a site that never looked at this.

If you want a second set of eyes on this, that is part of what we do — see Webflow website development and website redesign — but the Lighthouse check above costs nothing and takes less time than reading this sentence twice. Run it today.