Accessibility Overlays: Why the Widget Won't Save You

Someone is emailing you right now offering ADA compliance for the price of a phone plan. One line of JavaScript, a little blue accessibility icon in the corner of your site, and a certificate saying you are protected. It is a very good pitch.

It is also why 983 lawsuits in 2025 landed on websites that already had the widget installed.

Here is the honest version, with receipts. An overlay does something real. It just does not do the thing the sales page implies — and the gap between those two things is exactly where the demand letter arrives.

Do accessibility overlays actually make a site compliant?

No. The Overlay Fact Sheet, signed by 1,031 accessibility practitioners — including contributors and editors of the WCAG, ARIA, and HTML specifications, plus contributors to the JAWS and NVDA screen readers — states it flatly: 'While the use of an overlay may improve compliance with a handful of provisions in major accessibility standards, full compliance cannot be achieved with an overlay.'

The people who build the standard, and the people who build the screen readers the standard exists to serve, are on the same side of this. That is unusual, and it should tell you something.

In WebAIM's survey of web accessibility practitioners, conducted in January 2021 with 758 respondents, 67% rated overlay tools as 'not at all' or 'not very' effective. Among respondents who themselves have disabilities, that rose to 72%.

And there is no certificate to buy in the first place. The Department of Justice's own web accessibility guidance says businesses 'have flexibility in how they comply' and that DOJ 'does not have a regulation setting out detailed standards.' No federal body certifies a private business's website as ADA compliant. So when a vendor hands you a compliance badge, understand precisely what it is: a document the vendor printed about itself.

What does an overlay genuinely do?

It handles roughly half of the machine-detectable problems, by the vendors' own accounting. AudioEye's plans page describes its automated tier as 'Automated tools addressing ~50% accessibility issues,' with a footnote that it 'does not include expert testing for remaining issues.' That is the vendor's own number, on the vendor's own pricing page.

Strip the marketing away and an overlay is two things bolted together:

• A user-preference panel. Contrast modes, bigger text, wider letter spacing, a larger cursor, a reading guide. These are genuinely useful to some people, and they are also things most operating systems and browsers already do.
• An automated remediation pass. A script that scans your DOM and guesses at fixes — inferring ARIA roles, generating alt text for images, adding a keyboard-navigation mode.

That is not nothing. If your site is already structurally sound, a widget is a mildly useful preferences panel that some visitors will click. The problem is not that overlays exist. The problem is that a preferences panel is being sold as a legal shield.

What can an overlay provably not fix?

You do not have to take an activist's word for this — the exclusion list is published by the vendor. accessiBe's own excluded issues page states that neither accessWidget nor accessFlow remediate PDFs, Word files, spreadsheets, audio files, video files, or SVGs; content inside third-party iframes 'such as for payment processing'; CAPTCHA elements; images where the text is baked into the picture; or keyboard layouts other than QWERTY.

Now read that list against your actual website:

A dental practice's new-patient forms are a PDF. A med spa's booking flow is an iframe. A restaurant's menu is a photograph of a menu. A law firm's contact form has a CAPTCHA on it. Every single one of those is on the vendor's own excluded list — and every single one is exactly what a plaintiff's tester screenshots.

The widget is loudest about the barriers it is quietest about fixing.

Why has the FTC taken action against an overlay vendor?

On January 3, 2025, the FTC announced an order requiring accessiBe to pay $1 million to settle allegations that it misrepresented the ability of its AI-powered accessWidget to make any website compliant with the Web Content Accessibility Guidelines.

Samuel Levine, Director of the FTC's Bureau of Consumer Protection, put it this way: 'Overstating a product's AI or other capabilities without adequate evidence is deceptive, and the FTC will act to stop it.'

The order bars the company from representing that its automated products 'can make any website WCAG-compliant or can ensure continued compliance with WCAG over time, unless it has the evidence to support such claims.' Sit with that. The exact promise that sells the widget is the promise a federal regulator ordered the vendor to stop making.

There is a second half to the complaint that matters more than the fine, and almost nobody mentions it. The FTC also alleged that accessiBe 'deceptively formatted third-party articles and reviews to appear as if they were independent opinions by impartial authors' and failed to disclose its material connections to those supposedly objective reviewers.

So when you googled 'do accessibility overlays work' and found a reassuring review, consider the possibility that you were reading marketing. The whole search result for this question is structurally conflicted: the buyer asking 'does this work' is being answered, at scale, by the seller.

Do sites with overlays still get sued?

Yes. Of the 3,948 ADA website accessibility lawsuits EcomBack tracked in 2025, 983 — 24.90% — were filed against websites that already had an accessibility widget installed. By vendor: accessiBe 424 lawsuits, UserWay 273, AudioEye 88.

Read that number carefully, because it is easy to overstate in both directions. It does not mean a quarter of overlay customers get sued. It means that among the lawsuits actually filed, roughly one in four landed on a site that had already bought the protection. The widget was live. The icon was in the corner. The letter came anyway.

Vendors answer this with a pledge, not a fix. accessiBe's published plans list 'Comprehensive Litigation Support' with a '$15k Pledge' starting on the $1,490/year tier and a '$20k Pledge' above it — the $490/year entry plan carries no litigation support at all. AudioEye's Assurance is described as 'limited, guaranteed financial protection against WCAG-related demand letters and/or lawsuits' — and its own footnote says it 'requires purchase of a Managed package,' so the automated widget alone does not carry it.

A capped, conditional indemnity is a real product. It is just not the product you thought you bought. You wanted an accessible website. You were sold a partial insurance policy against the consequences of not having one.

Overlay subscription vs one-time remediation: which costs less?

The published overlay tiers run from $490/year to $3,990/year — and you pay that every year, forever, for a script that stops loading the day you stop paying.

The verdict: spend the money on remediation, not the subscription. An overlay is the only line on that table you rent forever, and the category's biggest vendor has already been fined $1 million for overstating what it does. If you still want the widget, buy it as a preferences panel for your users. Never buy it as a defense.

The real math is not which invoice is bigger this month. An overlay is rent: the JavaScript loads because you paid, and on the day you cancel, your site is exactly as broken as it was before you started. Remediation is capital: you fix the form labels, the heading order, the focus states, the contrast, in your own code — and they stay fixed whether or not anyone is invoicing you.

Also notice which vendor on that table will not publish a price. 'Call for a quote' is a red flag in accessibility software for the same reason it is a red flag in agency pricing: the number depends on what they think you will pay.

What should you buy instead, and in what order?

Fix the four boring things that account for most machine-detectable failures — form labels, alt text, keyboard focus, and text contrast — before you spend a dollar on a widget. In practical order:

• Scan it free first. axe DevTools, WAVE, or Lighthouse will find the machine-detectable issues in an afternoon. This is the same class of automated tool the overlay runs — you are just seeing the output instead of paying to have it hidden.
• Fix the four boring ones in your own HTML. Label every form input. Write real alt text. Make every interactive element reachable and visible with a keyboard. Get your text contrast up.
• Have a human test it. Tab through the site with a keyboard, then run it with a screen reader (NVDA is free). Automated tools do not catch a form field that is technically labeled 'field_2'.
• Handle the excluded list. Your PDFs, your iframes, your uncaptioned video, your image-of-a-menu. The overlay's own documentation admits it never touches these, so they are yours regardless.
• Publish an honest accessibility statement. Say what you have done, what you know is still imperfect, and give a real phone number and email for reporting a barrier. Then actually answer it.
• Only then, if you want, add the widget — as a user-preference panel, labeled as such, with no compliance claim attached to it.

The awkward truth for most service businesses is that accessibility failures are baked into the template, not sprinkled on top of it. If your theme ships with unlabeled inputs, a keyboard trap in the mobile nav, and light-grey text on white, no script bolted to the front is going to save you. That is why we handle accessibility inside conversion-focused website design rather than selling it as an add-on.

There is a bonus you should not ignore: a semantic, keyboard-navigable, properly-labeled site is the same site that loads fast and converts. Clean markup, fewer blocking scripts, real headings, forms that make sense. The work overlaps almost completely with what page speed does to your conversion rate, and an honest accessibility statement is itself one of the trust signals that actually convert.

One last thing, because it is the same sentence twice. Anyone who guarantees you ADA compliance is doing exactly what an SEO who guarantees you a #1 ranking is doing: selling certainty over an outcome they do not control. There is no federal certification. No court has blessed anybody's badge. And the FTC just fined the biggest vendor in the category $1 million for saying otherwise.

If you do not actually know what is broken on your site, do not buy a widget to cover it up — get it measured. We look at accessibility, speed, and conversion in the same pass, because on a real website they are the same problem. Start with conversion-focused website design, or just have us look at what you have today. Get my free audit.