The ADA Lawsuit Tax: When an Unscanned Page Becomes a $75,000 Demand

This is litigation by volume, and you're in the pool

Web accessibility lawsuits are not rare, bespoke events. They are a high-throughput legal pipeline. Per Seyfarth's ADA Title III tracking and EcomBack's 2025 annual report, 3,948 website accessibility lawsuits were filed in federal court in 2025,23.8% more than 2024, and website cases made up about 36% of all ADA Title III federal filings. Count state courts and the total tops 5,000.

The plaintiff economics are what make this a systemic risk rather than a tail risk. Just 33 plaintiffs filed 1,978 lawsuits, over 50% of the total in 2025. These are repeat filers running templated complaints against sites they often discover through automated scanning. And being sued once is not the end: of the 5,000+ digital accessibility suits in 2025, 1,427 targeted companies that had already faced a prior claim. Remediate badly and you simply re-enter the pool.

The real cost is bigger than the settlement

Headline settlements understate the damage. Most cases settle within 60-90 days for $10,000-$25,000, but the all-in cost, settlement plus defense fees plus court-mandated remediation, lands at $45,000-$75,000, with complex cases and repeat exposure pushing well past $200,000. Then there are the costs that never appear in the legal invoice:

• Demand letters that never become lawsuits. A large, unreported volume of claims is settled privately under the pressure of a demand letter, particularly common in Pennsylvania and California.
• Emergency remediation. Fixing accessibility under a court deadline costs far more than building it in.
• Lost customers. The ~27% of adults with a disability are also buyers; an inaccessible checkout is abandoned revenue every day it ships.

The violations that trigger suits are the scannable ones

Here's the leverage. The WCAG failures cited in the overwhelming majority of complaints are not subtle, judgment-call issues. They are the same handful of machine-detectable defects, over and over:

• Images without alt text, screen readers announce nothing.
• Insufficient color contrast, the single most common cited violation, and usually a brand-palette choice.
• Form inputs without labels, unusable with assistive tech.
• Missing or wrong ARIA, broken roles and states.
• Keyboard traps, focus that can't escape a widget.
• Empty links and buttons, "link, link, link" with no destination announced.

An automated scan against the WCAG 2.1/2.2 ruleset catches the large majority of these before a plaintiff's scanner does. It won't catch everything, some criteria require human judgment, but it closes the exact gaps that templated complaints are built on.

# The shape of an automated accessibility pass (axe-core style)
import { AxePuppeteer } from '@axe-core/puppeteer';

const results = await new AxePuppeteer(page)
  .withTags(['wcag2a', 'wcag2aa', 'wcag21aa', 'wcag22aa'])
  .analyze();

for (const v of results.violations) {
  console.log(`${v.impact.toUpperCase()}  ${v.id}: ${v.help}`);
  console.log(`  ${v.nodes.length} instances · ${v.helpUrl}`);
}
// Gate: zero 'critical' or 'serious' violations ships
const blocking = results.violations.filter(v => ['critical', 'serious'].includes(v.impact));
if (blocking.length) process.exit(1);

The deadline that turns risk into obligation

Beyond US litigation, the European Accessibility Act became enforceable in June 2025, extending accessibility obligations to a broad set of digital products and services sold into the EU. For many companies this converts accessibility from "litigation risk to manage" into "compliance requirement to meet, " with penalties and potential market exclusion attached. The remediation work is the same, and it starts with knowing where you stand.

The bottom line

Web accessibility lawsuits are frequent, templated, geographically spreading, and built almost entirely on a short list of machine-detectable WCAG failures. The all-in cost per claim dwarfs the cost of remediation, and a single settlement often invites the next. Scan your site against WCAG 2.2, fix the critical and serious findings, gate new deploys so they can't regress, and treat the EAA deadline as the forcing function it is. The cheapest accessibility program is the one that runs before the plaintiff's scanner does.