Web Accessibility as a P&L Line: Cost Center or Lawsuit Insurance?

Most operators meet web accessibility the same way: an email lands, it's a demand letter or a filed complaint, and suddenly a line item you never budgeted for is quoting five figures. The instinct is to search "accessibility compliance," land on a vendor page, and buy the $490/year widget that promises to fix everything overnight.

That instinct is the mistake. Not because accessibility doesn't matter — because the product being sold to you was built to close a fear, not a gap. This article treats accessibility the way you treat every other operational risk: as a number you can estimate, a cost you can compare, and a decision you can stage. (This is risk framing, not legal advice — when a demand letter actually arrives, talk to a lawyer.)

How real is the lawsuit risk?

Start with the base rates, because vendor pages inflate them and skeptics dismiss them, and both are wrong.

In the first half of 2025, plaintiffs filed 2,019 federal digital-accessibility lawsuits — on pace for roughly a 20% increase over 2024, according to UsableNet's midyear report. Include state courts (New York and California especially) and the full-year 2025 count crosses 5,000. The trend line since 2018 has never reversed. It compounds.

Two numbers matter more than the headline for an operator sizing their own exposure:

• 69% of these suits target eCommerce. If you sell online, you are in the primary blast radius, not adjacent to it.
• 64% of defendants had revenue under $25M. The share of larger defendants is rising — plaintiffs increasingly target companies that can pay — but the majority are still small and mid-sized stores. The "we're too small to notice" defense is empirically false.

Here is the part the raw counts hide. There are millions of eCommerce sites in the US and roughly 5,000 filed suits a year, so the probability that any single store gets a filed federal lawsuit in a given year is a fraction of a percent. That sounds reassuring until you understand two things.

First, filed lawsuits are the tip. Demand letters — the pay-us-to-go-away emails that never reach a docket — run at many multiples of filed cases. They don't show up in any public count, which is exactly why they're the more common way you'll actually get hit.

Second, the probability is not evenly distributed. Plaintiff firms and their testers scan for patterns: common platform themes, missing alt text, checkout flows that fail keyboard navigation, video without captions. In 2025, 46% of federal cases involved repeat defendants, and 1,427 suits targeted companies that had already been sued. Targeting is systematic, not random. Your traffic, your visibility in search, and the accessibility of your checkout drive your real exposure far more than your revenue tier does.

So the honest answer: for a low-traffic store, annual probability is genuinely low. For a store with real traffic, real search visibility, and an unaudited checkout, it is high enough that ignoring it is a bet you're quietly making with your P&L.

What does an accessibility claim actually cost?

You cannot decide anything without the cost of the event. Here is the range, sourced from settlement trackers and defense-side reporting, not vendor scare copy.

• Demand letter, settled quietly: ~$5,000 is the common settlement figure, though early resolution can land between $1,500 and $5,000 depending on how fast you settle and who's representing you.
• Out-of-court settlement after filing: averages around $30,000, with demands ranging $5,000–$50,000 based on your size and jurisdiction.
• Defense legal fees: $30,000–$175,000 on top, in nearly every case that doesn't settle at the letter stage.
• Court judgment or class action: $85,000 to $400,000+.

Then the part everyone forgets: you still have to fix the site. Settlement agreements almost always require actual remediation on a deadline, plus a monitoring period. So the "cheap" path — ignore, get a letter, settle — costs you the settlement and the defense time and the remediation you were trying to avoid. You pay twice, under a court-imposed clock, with a plaintiff's expert grading your work.

This is the same dynamic covered in the true cost of eCommerce cybersecurity: the incident isn't the expensive part. The forced, time-boxed, adversarial cleanup is.

Do accessibility overlays actually protect you?

This is where the SERP lies to you, so read this section twice.

An overlay (or "widget") is a snippet of JavaScript you paste into your site. It loads a floating accessibility icon and claims to auto-detect and fix WCAG failures — contrast, alt text, keyboard traps — in real time. accessiBe, AudioEye, UserWay, and others sell this for a few hundred to a few thousand dollars a year. The pitch is irresistible to a busy operator: one line of code, "instant compliance," legal protection, done.

The data says it does not work as sold.

In full-year 2025, 983 lawsuits — roughly 25% of all filed cases — were filed against websites that already had an accessibility widget installed, up from 722 (about 23%) in 2024. The number of sued-with-a-widget cases is growing, both in count and as a share. Installing an overlay did not move these defendants out of the target set. In some accounts it moved them in, because overlays are detectable and their known failure modes give a tester a fast, documentable barrier to cite.

Then the regulator weighed in. In January 2025 the FTC ordered accessiBe — one of the largest overlay vendors — to pay $1 million for deceptively marketing its accessWidget product as something that would "automatically" make any website comply with WCAG 2.1 AA. The Commission also alleged accessiBe dressed up its own promotional content as independent third-party reviews. The final order, approved in April 2025, bars the company from claiming its automated product can make a site compliant without evidence to back it.

Sit with what that means for your risk file. The core selling claim of the category's biggest player was found deceptive by a federal agency. If you bought that promise and got sued anyway, the overlay is not your shield — it can become the plaintiff's exhibit that you were told a fix existed and chose the $490 version.

Why do overlays fail? Real accessibility lives in your HTML semantics, focus order, form labels, and how your components behave with a screen reader and a keyboard. An overlay sits on top of that DOM and tries to patch it at runtime. It cannot reliably infer what an unlabeled button does or what an image means. Worse, its own control panel frequently interrupts screen-reader navigation — making the site harder to use for the exact people it claims to serve. That is why disability advocates, not just plaintiffs, reject them.

When is remediation worth funding?

Here is the framework the vendor pages don't want you to run, because it produces "buy nothing" for some stores and "don't buy the widget" for the rest.

Treat accessibility as an insurance decision. Compare your expected annual legal cost to the one-time cost of real remediation.

Expected annual legal cost = P(targeted this year) × blended cost per event.

• P(targeted) is your honest probability of a demand letter or suit in a year. Drive it from traffic, search visibility, jurisdiction (NY/CA/FL raise it), and whether your checkout survives keyboard-only navigation — not from revenue alone.
• Blended cost per event is a realistic mix: mostly demand-letter settlements (~$5k) with a tail of filed-suit settlements ($30k) and defense fees ($30k–$175k). A defensible blended figure for a small-to-mid store is $15,000–$40,000, because the tail is fat.

Then remediation. A genuine WCAG 2.1/2.2 AA effort — audit, code fixes, a re-test — runs roughly $5,000–$50,000 depending on site complexity, one time, with modest ongoing cost to hold the line. Unlike an overlay, that spend is an asset: it lowers future probability, it's the thing a settlement would force you to do anyway, and it improves conversion for every keyboard, screen-reader, low-vision, and mobile user you were silently turning away.

The decision rule, staged by revenue and traffic:

• Under ~$250K GMV, low traffic: Monitor. Expected cost is likely below remediation cost this year. Do the free 20% — semantic HTML, alt text on product images, labeled form fields, visible focus states, keyboard-testable checkout. Do not buy an overlay. Revisit at your next traffic step-change.
• ~$250K–$1M GMV: Stage it. Run a real audit ($1,500–$5,000), fix the checkout and top templates first — that's where testers look and where lost conversions hide — then work down the priority list over a quarter. Expected cost is now in the same range as remediation, and remediation is the appreciating asset.
• Above ~$1M GMV with real traffic: Remediate now. Your expected annual exposure has almost certainly crossed one-time remediation cost, and you have the revenue base plaintiffs increasingly target. Bake WCAG 2.1/2.2 AA into your definition of "done" for every new template and component so it stops being a project and becomes a standard.

Two operational notes that decide whether this holds.

Build it in, don't bolt it on. Retrofitting accessibility into years of accumulated markup is expensive for the same reason any eCommerce tech debt is expensive — the cost compounds the longer you defer, and it touches everything. The cheapest accessibility is the kind your components ship with by default. If you're replatforming or building new templates, the marginal cost of doing it right is near zero; the cost of adding it later is the audit-and-remediate bill above.

Watch the integration surface. Third-party widgets — reviews, chat, popups, buy-buttons — are a common source of accessibility failures you didn't write and can't fully control, the same way they're a source of hidden operational cost in the integration tax. Every embed is a surface a tester can cite. Audit them the way you'd audit any dependency.

What you actually get besides insurance

The pure risk framing undersells it, so name the upside honestly. Accessible sites are more usable sites. Keyboard navigation, clear focus states, proper labels, and logical structure help every user under load — on mobile, on bad connections, in a hurry. The same structural discipline that makes a site screen-reader navigable makes it more findable and more shoppable, which is the throughline in site search and navigation ROI. You are not just buying down legal exposure. You are removing friction from the funnel for a slice of customers — one in four adults report a disability — you were quietly excluding. That's revenue, not charity.

FAQ

Will an accessibility overlay protect me from a lawsuit?

No. In full-year 2025, about 25% of filed accessibility lawsuits targeted sites that already had a widget installed, and that share is rising. The FTC fined the largest overlay vendor, accessiBe, $1 million in 2025 for deceptively marketing its tool as a compliance guarantee. An overlay does not fix the underlying code, and in a dispute it can serve as evidence you were aware of the issue and chose a cosmetic fix.

How much does real remediation cost versus getting sued?

Genuine code-level remediation to WCAG 2.1/2.2 AA typically runs $5,000–$50,000 one time, depending on site complexity. A lawsuit commonly costs ~$5,000 to settle a demand letter, ~$30,000 for a post-filing settlement, plus $30,000–$175,000 in defense fees — and you still have to remediate afterward on a court deadline. For most stores with real traffic, remediation is cheaper than the expected cost of an event, and it's an asset rather than a sunk fee.

What is WCAG and which version do I need?

WCAG (Web Content Accessibility Guidelines) is the W3C standard courts and settlements treat as the practical benchmark. It has three conformance levels — A, AA, AAA — and the operative target is Level AA. WCAG 2.2 became a W3C Recommendation in October 2023 and builds on 2.1 without replacing it; meeting 2.2 AA also satisfies 2.1 AA. Aim for 2.1/2.2 AA.

I'm a small store with low traffic. Do I really need to spend on this?

Maybe not this year — and that's a legitimate, deliberate decision, not negligence. If your traffic and search visibility are low, your expected annual exposure may fall below the cost of full remediation. In that case: do the free fundamentals (semantic HTML, image alt text, labeled forms, visible focus, keyboard-testable checkout), skip the overlay, and re-run the math at your next traffic step-change. What you should not do is buy a widget and assume you're covered.

Where does accessibility risk actually concentrate on my site?

The checkout and conversion path first — keyboard traps, unlabeled form fields, and inaccessible payment steps are both the most-cited barriers and the ones costing you real sales. Then product templates (missing alt text, poor contrast, non-navigable galleries), then third-party embeds you didn't build. Fix in that order; it aligns legal exposure with revenue recovery.