Every public-facing MVP is already in scope for ADA Title III accessibility lawsuits — there's no revenue or user-count threshold to cross. Plaintiffs filed 3,117 federal accessibility lawsuits in 2025, up 27% year over year; courts treat WCAG 2.1 AA as the benchmark. Building it in from day one costs $800-$5,000; a demand letter after the fact costs $15,000-$110,000+.
Founders hear "ADA compliance" and think of ramps and parking spaces, not code. Wrong mental model. Title III of the Americans with Disabilities Act covers "places of public accommodation," and every federal circuit that has ruled on the question in the last decade has extended that phrase to commercial websites — with zero carve-out for a two-week-old MVP with a hundred signups. Unlike CCPA's 100,000-consumer trigger or SOC 2's enterprise-deal trigger, there's no size gate here. A single visually-impaired visitor using a screen reader is standing to sue the day you launch.
This note is the exposure test, the tiered cost table, and the one build decision — accessible markup versus an accessibility widget — that determines whether a demand letter costs you a week or a year.
Does your MVP actually need ADA/WCAG accessibility compliance?
Skip the threshold-hunting. If any of these is true, you're exposed today:
- Your site is public-facing and commercial. No revenue floor, no user-count floor. The exposure test that applies to CCPA or SOC 2 doesn't exist here — a pre-revenue MVP with a marketing page is already a "place of public accommodation" under the prevailing circuit-court reading of Title III.
- You serve any U.S. state, not just California. ADA is federal. State-level accessibility statutes (California's Unruh Act, New York's Human Rights Law) stack additional statutory-damages exposure on top of the federal claim in those states specifically.
- You've had zero accessibility audit, ever. Most sued businesses find out they're non-compliant from the demand letter, not from an internal review. Retail, food service, hospitality, and home-goods sites got hit hardest in 2025, but no industry has been exempt.
There's no "out of scope, for now" answer here the way there is with CCPA. The only lever you control is whether the first accessibility issue is found by your own build process or by a plaintiff's attorney.
What does ADA/WCAG compliance actually cost?
| Tier | What it covers | Rough cost |
|---|---|---|
| Baseline, built-in | Semantic HTML, keyboard navigation, alt text, color-contrast checks, and an accessibility statement, built into the MVP from week one | $800-$5,000 (mostly engineering time, not a separate line item) |
| Reactive, post-demand-letter | A rushed third-party audit, developer remediation under deadline, and legal review of the response | $15,000-$110,000+ |
| Litigated | Settlement plus defense fees after a filed lawsuit, even when no actual damages are proven | $60,000-$200,000+ |
Costs as of September 2026. Demand letters alone typically settle for $5,000-$25,000 before any court filing; defending a lawsuit that never reaches a damages finding still runs $5,000-$125,000 in legal fees on its own.
Why do accessibility overlay widgets increase lawsuit risk instead of reducing it?
Overlay widgets — the small "accessibility" icon that promises one-click WCAG compliance via a JavaScript layer — are the single most common thing founders buy when they panic-read about ADA exposure, and they're the wrong purchase. In the first half of 2025, 456 lawsuits, 22.64% of all filings, targeted websites that already had an accessibility widget installed. Widget-equipped sites got sued at a rate that increased every month against the same period in 2024. Screen-reader users and disability advocates have documented for years that these overlays paper over markup problems instead of fixing them, and plaintiffs' attorneys now know it — a widget badge on a site can read as evidence the business knew it had a problem and bought a shortcut instead of a fix.
The overlay is a compliance-theater expense that doesn't reduce the underlying legal exposure it claims to. That's the sentence worth remembering before you install one.
What's the one build decision that actually sets the bill?
Building to WCAG 2.1 AA in the markup itself, not bolting an overlay on top of it. Semantic HTML elements, a real keyboard-navigable tab order, alt text written at build time (not auto-generated after the fact), sufficient color contrast, and form labels that a screen reader can actually parse — none of this is exotic engineering. It's the same discipline we apply to GDPR's data-processing register: an architecture decision made in week one, when it costs a few hours of a frontend engineer's time, not a scramble after a demand letter names your company.
The DOJ's own rule for state and local government sites sets WCAG 2.1 Level AA as the compliance floor, and federal courts have converged on that same standard as the practical benchmark for private commercial sites under Title III, even without a matching private-sector regulation on the books. Build to that standard once and the demand-letter conversation is short: you point to the audit, not to a shortcut.
Can a product studio build an ADA/WCAG-compliant MVP?
Yes, and it's mostly a discipline problem, not a technology problem: semantic components from the design system up, alt text as a required field before a page ships, and an automated accessibility check in the same CI pipeline that runs the test suite. What a studio won't do is promise a widget will make a legal risk disappear, or sign off that a site is "ADA certified" — there is no such certification, and any vendor selling one is selling the same compliance theater the overlay market already sells.
The founders who get sued treat accessibility as a checkbox added after launch. The ones who don't treat WCAG 2.1 AA as a rendering requirement, checked in the same pull request as everything else.
Written 2026-09-11 by Naman Barkiya.