Why Accessibility Overlay Widgets Do Not Work
One line of JavaScript, compliance solved. Except the lawsuit numbers went up, and the FTC fined the biggest vendor $1M.
The pitch, and why it works
You paste one line of JavaScript into your site. A small icon appears in the corner. According to the marketing, an AI now scans your pages, repairs the accessibility defects, and keeps you compliant as you publish new content. The price is a subscription rather than a remediation project, and it takes an afternoon rather than a quarter.
It is an extremely good pitch. It is aimed at a business owner who has just received a demand letter, does not have a developer on staff, and has been quoted five figures by an agency. Of course it sells.
The problem is not that overlays are useless at everything. It is that the specific promise — automated compliance — is one no software can keep, and the evidence that it is not being kept is now unusually well documented.
The FTC action
In January 2025 the Federal Trade Commission announced that accessiBe, the largest overlay vendor, would pay $1,000,000to settle allegations of deceptive marketing. The FTC’s complaint alleged that accessWidget did not make websites WCAG-conformant as advertised, and that it failed to make basic components — navigation menus, form fields, image descriptions — accessible.
The complaint also alleged that the company had presented reviews, articles and blog posts as independent endorsements when it had undisclosed material connections to the people and organizations behind them. The final order, approved in April 2025, bars accessiBe from representing that its automated products can make any website WCAG-conformant, or keep it conformant over time, without evidence to support the claim.
This matters beyond one company. It is a regulator stating, on the record, that automated remediation claims are actionable when they are not substantiated.
Sources: FTC, January 2025 · FTC final order, April 2025.
The lawsuits did not stop
The clearest test of “does this protect me” is whether the sites using it are being sued. They are. Websites running overlay widgets were named in more than 400 ADA lawsuits in 2024, and nearly 500 in the first half of 2025. That is not a story about a few outliers; it is a rate.
And it makes sense mechanically. A plaintiff’s tester does not evaluate your subscription. They open the site with a screen reader and try to complete a task. If the task cannot be completed, the presence of a widget is not a defense — and occasionally it is part of the allegation.
Why it fails, technically
This is the part that usually gets skipped, and it is the part that makes the rest inevitable rather than unlucky.
It cannot know what your content means
The most cited defect is images with no text alternative. To fix that you must know what the image conveys in this context. A photograph of a person on an About page is decorative; the same photograph on a staff directory is informative and needs the person’s name. Image recognition can say “a man in a blue shirt”. It cannot know that the correct alt text is “Dr Sarah Chen, Chief of Cardiology”, and a confidently wrong description is worse than an empty one because the user has no signal that they are missing something.
It fights the user’s own software
A screen reader user is not arriving without tools. They arrive with JAWS or NVDA or VoiceOver, configured the way they like it, and years of muscle memory. An overlay that injects its own ARIA attributes, its own focus management and its own keyboard shortcuts is not adding accessibility to a blank slate — it is contending with a working setup. This is the specific reason disability organizations object, and it is why some users install blockers for these scripts.
It runs after the fact, in the browser
The widget executes on page load, after your markup has already been sent. Anything that depends on the underlying document structure — a form field that has no associated label in the HTML, a button that is really a div, a heading order that does not exist — is being patched from the outside by guesswork. Fixing it at the source is one line of HTML. Guessing it at runtime is a heuristic that will sometimes be wrong and will never tell you when.
It cannot fix what it cannot see
Keyboard traps, focus visibility, reading order, whether an error message is comprehensible, whether captions are accurate — none of these are detectable automatically, so none of them are repairable automatically. They are also a large share of what actually stops people using websites.
What to do instead, at each budget
The honest version of the overlay pitch is that people want a cheap first step. That is a reasonable thing to want, and it exists — it just is not a widget.
- Free. Scan a page and find the machine-detectable failures. The scan here is free and ranks findings by how often each issue gets cited. Then do the ten-minute keyboard pass yourself.
- An afternoon. Fix alt text, form labels, control names, page language, page titles and heading order. These are edits, not projects, and they are what the complaints are built from.
- A few days of developer time. Contrast, focus indicators, keyboard operability of custom components, captions on video. This is where most real barriers actually live.
- A real budget. A human audit with actual assistive technology, ideally including testing by disabled users. This is the only thing that gets you a defensible position, and it is what a VPAT is supposed to be based on.
A published accessibility statement — what you have done, what is outstanding, and a working way to report a barrier to a human — costs nothing and is worth more than a subscription. It is not a legal shield, but demonstrable good faith with a real contact route beats a widget and silence.
The bottom line
Overlays are sold as a substitute for the work. The regulator has fined the largest vendor for saying so, the lawsuit numbers for overlay-using sites went up rather than down, and the people the widgets are supposed to help have publicly asked the industry to stop. Spend the money on the markup.
Frequently asked questions
Do accessibility overlays make a website ADA compliant?
No. No automated tool can, and the largest overlay vendor has been ordered to stop saying otherwise. In January 2025 the FTC required accessiBe to pay $1,000,000 over claims that its accessWidget product could make any website WCAG-conformant; the final order, approved in April 2025, bars the company from repeating those claims without evidence to support them.
Will an overlay stop me getting sued?
The data says it does not. Websites running overlay widgets were named in more than 400 ADA lawsuits in 2024 and nearly 500 in the first half of 2025 alone. Installing one is not a recognized legal defense, and in some cases plaintiffs have cited the overlay itself as part of the barrier.
Why do disability organizations oppose overlays?
Because they frequently interfere with the assistive technology the user already has and has configured. A screen reader user arrives with their own software, their own settings and their own keyboard habits. An overlay that injects its own ARIA, its own focus handling and its own keyboard shortcuts on top of that can make a workable page unusable. The National Federation of the Blind has passed a resolution against accessiBe specifically, and thousands of accessibility practitioners have signed a public statement opposing overlays as a class.
Is there any legitimate use for a widget like this?
A genuine preferences panel — larger text, higher contrast, reduced motion, all applied to your own site and built by you — is a real accessibility feature and some users like it. That is different in kind from a third-party script that claims to detect and repair your markup automatically. The first is a feature. The second is a claim.
Keep reading
- ADA Website Compliance, Explained Without the Legalese — There is no federal web rulebook, yet thousands of suits get filed every year. Here is what is actually being enforced, and against whom.
- WCAG 2.2 Level AA in Plain English — The spec is written for standards bodies. This is the same requirements written for whoever has to go and change the site.
- How to Write Image Alt Text That Actually Helps — The most-cited failure in ADA complaints, and the one most often "fixed" in a way that makes things worse.
Nothing here is legal advice. Accessibility obligations vary by jurisdiction and by how a site is used. If you have received a demand letter, talk to a lawyer.