A long-standing client sent me their accessibility vendor's renewal proposal and asked the question I now get more than any other: is this worth what we're paying for it?
Theirs was a genuine remediation contract, so the answer was largely yes. But the question underneath it is the one most merchants can't answer, and it is why this article exists. The accessibility market sells two entirely different things under one word. The cheaper one does not do what buyers believe it does, and a lot of Shopify owners are holding it while assuming they're covered.
The short version: accessibility overlay apps, the kind that add a floating accessibility button and promise automated compliance, do not protect you from ADA lawsuits, and in some cases make you a bigger target. The only thing that resolves the risk is fixing the issues in your store's actual code. Here's why the widget is the wrong tool, and what to install instead.
A $59-a-month sense of safety
US merchants are being sued over web accessibility at industrial scale, and the filings are concentrated in very few hands. EcomBack's 2025 mid-year report counted 2,014 website-accessibility lawsuits filed in the first six months of 2025, up 37% year over year, with 31 plaintiffs and 16 law firms behind half of them. These firms increasingly send a cold "pre-suit" email first. Most owners only learn the category exists when one lands in their inbox.
So the appeal of an overlay app is obvious. Install a widget, it scans your site, it shows shoppers an accessibility menu, and the marketing copy implies you're now compliant. accessiBe prices accessWidget from $59 a month. For that, the problem feels handled.
It isn't handled. And the developers who do accessibility remediation, the people who get called in after a store gets sued, are close to unanimous on this.
Overlays don't stop suits, and sometimes start them
Three things are true about overlay widgets, and merchants are told none of them.
1. They don't prevent lawsuits. Sued stores had an overlay installed and running. In that same EcomBack half-year count, 456 of the 2,014 filings (22.6%) targeted websites that were already using an accessibility overlay or widget. If the widget worked, those suits wouldn't exist. The overlay sits on top of your site as a layer of JavaScript; it doesn't fix the underlying HTML that a screen reader actually reads. Assistive technology often bypasses the widget entirely and hits the same broken markup it always would.
2. A major vendor settled with a US regulator over exactly this promise. In January 2025 the FTC announced a settlement with accessiBe, maker of accessWidget, over its claim that the product could make any website compliant with the Web Content Accessibility Guidelines. The FTC's complaint alleged accessWidget "did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated," and separately alleged the company dressed up third-party articles and reviews to read as independent opinion while hiding its connections to the reviewers. The Commission approved the order as final on April 22, 2025: accessiBe pays $1 million, money the FTC says may be used to refund consumers, and is barred from claiming its automated products can make any site WCAG-compliant, or keep it compliant, without evidence to back it up.
The vendor is now barred from promising you the thing you bought it for, unless it can prove the claim.
accessiBe is also facing a putative class action from one of its own customers, a medical practice that says it installed the widget and received an ADA demand letter anyway (Sherwin K. Parikh MD, P.C. v. accessiBe, Inc., S.D.N.Y., filed June 2024). Attaching your brand to a tool that's itself under legal fire is the opposite of cover. In the words of one remediation specialist, it "paints a target on your back."
3. They can break the thing they're supposed to protect. I've heard first-hand accounts of an overlay breaking the checkout button for assistive-technology users. Think about what that means legally: a tool you bought to reduce risk took a working store and made its primary function unusable for exactly the users the law protects. There is no faster way to manufacture a valid complaint.
You can't bolt on something that has to be built in
Accessibility is a property of your store's structure: the heading order, the labels on form fields, the keyboard path through a menu, the contrast of your text, the alt text on your images. Those live in the theme and in the apps that inject markup into it.
An overlay can't change that structure. It runs after the page loads, as a cosmetic layer a sighted user can open. A screen-reader user navigating by headings and landmarks never sees the menu. They experience the raw page. So the widget improves the one thing that was never the problem (the visible UI for sighted users) and leaves untouched the thing that is (the underlying semantics).
This is the same reason "temporary overlay until we fix it properly" is a trap. There's no good version of a layer that intercepts your DOM and hopes for the best. If anything, it adds a second failure surface on top of the first.
What to do about it
1. Remove the overlay. It's not buying you protection, and it may be adding risk. This is usually the first thing I do on a remediation engagement.
2. Fix the issues at the source. This is the only thing that resolves a complaint, and every remediation specialist I know says the same. It's also more tractable than it sounds: most stores have a short list of repeated, theme-level defects (missing form labels, poor contrast, no keyboard focus styles, images without alt text) multiplied across many pages. Fix the pattern, fix the catalog.
3. Use real tools: testing tools, not widgets. The legitimate software in this space identifies and helps you fix issues at the source; it isn't a customer-facing button. Two I'd point you to: Accessibility Insights (free, from Microsoft, built on Deque's open-source axe engine) for finding issues, and Patrol for AI-assisted identification and remediation in your theme files. The distinction is the whole point. A tool your developer runs is useful; a tool your shoppers click is theatre.
4. Add a real accessibility statement. A short page in your footer acknowledging that accessibility is an ongoing effort, with a contact method for anyone who hits a barrier, is genuine good-faith evidence. It does more for you than any widget, and it costs nothing.
The bottom line
Owners want the math. Here it is, including the part most writing on this subject leaves out.
There is no trustworthy public figure for what an ADA website settlement costs. The organisations that track this litigation and publish their method (Seyfarth Shaw's ADA Title III blog, UsableNet's year-end report) count filings, not settlement dollars. The sources that do quote dollar figures are companies selling accessibility products, and they don't agree with each other. Accessible.org puts settlements at $5,000–$20,000, sourced to conversations with defence attorneys. TestParty puts the typical settlement at $30,000–$100,000+, with no stated method or sample. Developers I know who get called in after a filing describe merchants settling for a couple of thousand. That's a spread of more than an order of magnitude, and not one of those figures comes with a sample you can check. I'm not going to add a fourth invented number to the pile.
What isn't an estimate is the statutory floor. In California, a violation of the ADA is automatically a violation of the Unruh Civil Rights Act (Cal. Civ. Code § 51(f)), and Unruh sets damages at "in no case less than four thousand dollars ($4,000)" per violation, plus the plaintiff's attorney's fees (Cal. Civ. Code § 52(a)). That is the cheapest number the system can produce: one violation, in one state, before either side's lawyer bills an hour.
Set the cost of fixing it against that. An audit and the remediation pass that follows it close the gap for a fraction of the lowest damages figure a California court is permitted to award. And a floor is the least you'd pay, not the most.
The ratio isn't the real argument, though. A settlement doesn't make your store usable. Whatever you pay to make a complaint go away, the code work is still sitting there when you're done, so remediation isn't the alternative to a settlement, it's the thing you do first or the thing you do second at a worse price. It's also the only one of the two that leaves you with a store that works for the people the law is about. A widget subscription buys you neither, and bills you every month for the privilege.
One caveat worth stating plainly: I'm a developer, not a lawyer. What I can tell you is what the technology does and doesn't do, and what the public filings say. What any of it means for your specific exposure is a question for counsel.
If you've got an accessibility app on your store right now, the honest move is to find out whether it's doing anything. In my experience, the answer is: not what you were sold. If a cold accessibility email has landed in your inbox, or you want to know whether your store would survive a look, grab a slot and bring your store URL plus the name of whatever accessibility app you're running. The first thing I'll tell you is what it is and isn't doing.
