Key takeaways
- In 2025, plaintiffs filed 3,117 federal website accessibility lawsuits — up 27% from 2024 — and 64% of the companies sued earned under $25 million a year. Small businesses aren't collateral damage. They're the main event.
- Demand letters are triggered by a handful of machine-detectable failures: missing alt text, unlabeled form fields, low contrast, broken keyboard navigation. Fix those and you remove most of the reason anyone targets you.
- A $99 accessibility widget does not stop lawsuits — 26% of defendants sued in January 2026 already had one installed, and the FTC fined accessiBe $1 million over its marketing claims.
- Honest remediation for a typical small site runs $3,000–$8,000 — usually less than a single settlement, which commonly lands around $30,000.
- If a demand letter arrives: don't ignore it, don't reply yourself, get an ADA-experienced lawyer, and start documenting fixes through counsel.
If you've heard about the ADA website lawsuits, you've probably heard two versions of the story. The first is panic: "You're one demand letter away from a $50,000 lawsuit." The second is dismissal: "They only go after big companies."
Both are wrong. Here is what is actually happening, based on the filing data rather than the sales pitches.
The first version has a grain of truth. The second has none. Small businesses are not too small to get sued. They're the preferred target.
Who actually gets hit (and why it's you, not Target)
The numbers are public and they are not subtle. Seyfarth's ADA Title III tracker reported 3,117 federal website accessibility lawsuits filed in 2025, a 27% increase over 2024. January 2026 alone added 347 website cases across federal and state courts.
UsableNet's analysis of 2025 filings found that 64% of companies sued generated less than $25 million in annual revenue, and that e-commerce accounted for roughly 70% of cases. Your online store runs the same off-the-shelf theme components as a national chain's. Being small buys you a lower profile, not better markup.
And the pattern is industrial, not personal. EcomBack's January 2026 report found that the top 10 plaintiff firms filed 83% of that month's cases. Read that again. This is not one disabled user suing the business that wronged them. It is a small number of law firms running automated scanners across thousands of sites, generating demand letters the way an assembly line makes parts.
The bot doesn't see your budget. It sees your code. A plaintiff's scanner checks attributes and contrast ratios. It doesn't know you employ four people and care deeply about your customers. It only knows what your markup says.
Small businesses make better targets because the economics work: an owner who wants the problem gone before it touches payroll is more likely to settle than to litigate. The law firms know this. Your defense is not to be too small to notice. It's to have nothing for the scanner to find.
What actually triggers a demand letter
A demand letter names specific technical barriers — missing alt text, keyboard access failures, screen-reader incompatibilities. These are not design opinions a lawyer argues about in court. They are machine-detectable failures a script can flag on ten thousand sites before lunch.
Here is the priority list we use when we clean these up, ordered by how often each one shows up in scan output — and in demand letters.
| Trigger | What breaks for a real visitor | Typical fix effort |
|---|---|---|
| Missing alt text on informative images | A screen reader announces "graphic" or nothing — the visitor has no idea what the image says or sells | Content work; hours, not days |
| Unlabeled form fields | The visitor can't tell what information each box wants; placeholder text that disappears on focus is not a label | Developer hours; associating a <label> with an input is cheap |
| Low color contrast (below 4.5:1) | Pale grey or light blue text on white is unreadable for visitors with low vision | One line of CSS; check every color pair in your actual stylesheet, not on your monitor |
| Icon-only buttons with no accessible name | A cart button that's just an SVG announces as "button" — a dead end | Small developer fix per button |
| Keyboard traps (menus, date pickers, pop-ups) | Tab in with no way out without a mouse; whole flows — booking, checkout — become impossible | Medium developer effort; test every interactive element with Tab alone |
| Missing visible focus indicator | A keyboard user can't see where they are on the page | Small CSS fix |
| Form errors that don't explain themselves | "Invalid input" doesn't tell anyone what to fix; a quote request dies at submit | Developer + copy fix |
| Broken heading structure / missing page language | Screen readers navigate by headings; a page of <div>s reads as soup | Content + template fix |
| Third-party embeds (booking iframe, POS ordering widget) | Often the least accessible thing on the page — and you didn't write a line of it | May require pressuring or replacing the vendor |
| Video without captions | Deaf and hard-of-hearing visitors get nothing from your promo video | Captioning; cheap per video, expensive for a decade-long library |
Notice something: seven of the ten are found by a free automated scan in minutes. The remaining three need a human with a keyboard and a screen reader — because automated tools catch only about 30 to 57% of accessibility issues depending on the study. The scanner finds the cheap stuff. A person finds the rest.
The fixes that matter most are the cheapest ones. An
altattribute costs nothing. A<label>costs nothing. Darkening a button until it clears 4.5:1 costs one line of CSS. No one has ever successfully argued these are a "significant expense."
The "$99 ADA widget" won't save you
You've seen the ads: paste one line of JavaScript and your site becomes "ADA compliant overnight." Here's what those widgets actually do: they add a control panel on top of your existing code. They do not repair the underlying HTML, CSS, forms, or scripts. The screen reader still reads the broken markup underneath the panel.
The evidence is blunt. EcomBack reported that 26.22% of January 2026 cases involved sites already using accessibility widgets. The widget didn't cause the lawsuit. But it clearly didn't prevent it, either.
And the regulator has weighed in. In January 2025, the FTC ordered accessiBe to pay $1 million over marketing claims that its accessWidget product could automatically make websites WCAG compliant. A widget can be a visitor-experience add-on if you want one. It is not remediation, and selling it as one cost a company seven figures.
If your developer's entire accessibility plan is "we installed a widget," you don't have a plan.
What honest remediation actually costs
Now the part the scare-quote industry hates: real numbers. Accessibility vendors publish their pricing, so you don't have to guess — or believe anyone who tells you this is a $20,000 minimum problem.
| What | Typical cost | What you get |
|---|---|---|
| DIY: free scan + your own content fixes | $0–$500 | Alt text, labels, contrast, and a fix list you hand a developer — covers the machine-detectable triggers |
| Professional audit (small site) | $1,500–$3,500 | WCAG 2.1/2.2 AA review against your pages, prioritized report, fix roadmap |
| Audit + remediation (typical small business site) | $3,000–$8,000 | Findings fixed in the source code and re-tested — the whole job, done |
| Audit + remediation (e-commerce) | $15,000–$35,000 | Checkout, product templates, and transaction flows tested for keyboard and screen-reader use |
| Ongoing monitoring | $300–$500/month | Scans catch regressions before new content and plugins reintroduce barriers |
Compare that against the cost of doing nothing. Published ranges put demand-letter settlements at $3,000–$25,000, with many practitioners citing around $30,000 as a typical figure. Full litigation runs $10,000 to $150,000+. The ADA also requires the losing party to pay the plaintiff's attorney fees — which alone can run $10,000–$50,000.
Do the math: a proper remediation for a typical small site costs less than most settlements. And settlements don't fix your website — you still have to do the remediation afterward.
Prevention is cheaper than litigation, and it's not close. The remediation bill is a one-time project. The settlement bill is a tax on not having done the project.
One more thing almost nobody mentions: the money exists. The Disabled Access Credit (26 U.S.C. § 44) gives eligible small businesses 50% of eligible access expenditures between $250 and $10,250 — up to $5,000 a year. Eligible means gross receipts of $1 million or less in the prior year, or no more than 30 full-time employees. Separately, the Section 190 deduction allows up to $15,000 a year for barrier removal. Whether your specific invoice qualifies is a question for your accountant — but most owners have never heard either provision exists. Ask.
The demand letter just landed. Here's what to do.
Breathe. A demand letter is the start of a negotiation, not the end of your business. Here's the playbook, in order:
- Don't ignore it. Ignoring a letter is how a $5,000 problem becomes a $50,000 lawsuit. There are deadlines in that envelope.
- Don't reply yourself. Do not email the firm to explain, apologize, or argue. Respond through an attorney experienced in ADA defense — this is a specialized bar, and your general business lawyer probably isn't in it.
- Preserve everything. Screenshot your site as it stands today. Save any scans you've ever run. Your lawyer needs to know what the site looked like when the letter's claims were written.
- Start fixing through counsel. This is the part that actually reduces your exposure: scan the whole site (not just the homepage), fix the barriers that block real tasks, and document every fix with dates and retest results. A dated trail of good-faith remediation is what your counsel negotiates with.
- Negotiate a remediation timeline. Structured negotiation — a binding agreement to fix the site on a schedule — is far cheaper than litigation and it's the outcome most of these cases are built to reach.
- Publish an accessibility statement. A dated page that names the standard you're working toward (WCAG 2.2 AA), lists known limitations, and gives visitors a way to report problems. It documents effort and gives users a channel before lawyers get involved.
- Set up monitoring. New images, forms, and plugin updates reintroduce barriers quietly. A quarterly re-scan keeps you from sliding back into the crosshairs.
One California-specific warning: under the Unruh Civil Rights Act, statutory damages run $4,000 per violation — and each barrier can count as a violation. California filers know this math. If you do meaningful business in California, move faster.
The letter is a bill for work you haven't done yet. Almost every one of these cases ends the same way: you pay for the remediation you should have paid for earlier, plus the plaintiff's cut. The earlier you start the remediation, the smaller the cut.
The boring habits that keep you out of this
Nothing in this post requires heroics. The businesses that never get letters share three dull habits:
- Scan on a schedule. Quarterly is plenty for a site that doesn't change daily. Save the report, fix what it finds, re-scan.
- Gate new content. Alt text on images before publish. Labels on every new form field. Contrast checked before a new button ships. Ten minutes of discipline per page.
- Own your vendors. That booking iframe from your point-of-sale provider might be the least accessible thing on your site. Put accessibility in the requirements when you pick tools, and ask the question before you sign.
There's no federal regulation naming a WCAG version for private businesses — the DOJ has said so plainly and points to WCAG as "helpful guidance." In practice, courts and settlements use WCAG 2.2 Level AA as the benchmark. Build toward that and you cover whatever version a letter names.
What we'd do if this were our site
We build sites for small businesses — that's the whole business. If a client called us tomorrow with a demand letter, we'd do exactly this: run a scan on the money pages (homepage, services, contact, quote form, checkout), fix the machine-detectable failures first, keyboard-test every flow a customer can complete, publish an accessibility statement, and hand their lawyer a dated remediation log. In our experience, the first scan usually finds a few dozen failures and the fixes take a sprint, not a quarter.
If your site was built by a cheap theme, a page builder stacked with plugins, or an AI prototype that shipped fast and rough — the kind of code that we rescue every month — the accessibility debt is usually worse than the owner thinks. That's fixable too. It's just a project, not a catastrophe.
Want to know where your site stands before a law firm tells you? Run it through our free site audit — it'll find the barriers and tell you straight what they cost to fix. And if you've already got a letter in your inbox, book a call and we'll tell you honestly whether you need us, your lawyer, or both.
