Why Accessibility Overlay Widgets Don’t Make Your Site Compliant

The pitch is genuinely appealing, and I want to start by saying that, because plenty of sensible business owners have bought one and I am not interested in making anybody feel stupid.

Paste a single line of JavaScript into your site. A small accessibility icon appears in the corner. Visitors can click it to enlarge text, raise contrast, or turn on a reading guide. The vendor tells you the artificial intelligence behind it scans and repairs your site automatically, and for something like fifty dollars a month you are ADA compliant by tomorrow morning.

If accessibility could be solved that way, I would install one on every site I build and spend the time I saved somewhere else. It cannot, and this post is my attempt to explain why in a way you can verify rather than just take from me.

What an overlay actually is

An overlay is a script that loads after your page does and then tries to modify it in the browser. That timing is the whole story. Your actual website, the markup sitting on the server, is untouched. The overlay is a layer applied on top of it, in the visitor’s browser, every single time anybody loads a page.

So the question is not whether overlay companies are dishonest. The question is what a script arriving late to a page can and cannot repair.

What they genuinely can do, in fairness

Some of the toolbar features work fine and I am not going to pretend otherwise. Increasing text size, inverting colors, applying a dyslexia-oriented font, showing a reading ruler. These are real user preferences and the widget delivers them.

Two things are worth saying about that. Most of those features already exist in the browser and the operating system, generally implemented better, and people who need them are usually already using their own tools. And more importantly, none of those features are what WCAG conformance is made of. A contrast toggle is a nice convenience. It is not a substitute for your text meeting a contrast ratio in the first place.

What they cannot do, and why

Take the single most common failure on the web, an image with no alt text. To fix it, something has to write a description of what that image conveys in this context. Not “a photograph of a person,” but whether the image is decorative, or whether it is your pricing table rendered as a picture, in which case the alt text needs to carry the prices.

Automated image recognition can guess at subject matter. It cannot know intent. And a confidently wrong description is arguably worse than silence, because the user now believes they know what is there.

The same structural problem repeats across the standard:

• Form labels. A script can see an input box. It cannot reliably know that this particular unlabeled field is meant to be your policy number rather than your phone number.
• Reading and focus order. If your markup is out of order, the fix is reordering the source. Reshuffling it live is fragile and frequently makes the experience stranger.
• Headings and structure. Screen reader users move through a page by its headings. If your page uses styled bold text instead of real heading elements, there is no structure there to expose.
• Custom controls. A div styled to look like a button has no button behavior. Adding roles from the outside is guesswork about what the developer meant it to do.
• Keyboard traps in modals and menus. These come from how the component was written. An external script fighting that component tends to produce new bugs.

There is also a quieter problem. Overlays can interfere with the assistive technology a person is already running, because both are trying to manage the same page at once. Some screen reader users report that sites with overlays get harder to use, not easier, which is a bleak outcome for a product sold as help.

What the FTC said

This is the part that moved the argument out of professional opinion and into the public record.

In January 2025 the Federal Trade Commission announced an order requiring accessiBe, one of the largest overlay vendors, to pay $1 million to settle allegations that it misrepresented its product’s ability to make websites WCAG compliant.

The FTC also alleged the company had formatted paid and affiliated third-party reviews to appear as independent opinions, without disclosing the financial relationship. That second allegation is worth holding onto, because if you researched overlays a few years ago and came away reassured, it is worth asking what you were reading.

You can read the FTC’s own announcement rather than my summary of it. I would encourage that, and I would encourage the same skepticism toward me.

What disability advocates say

The objection did not start with regulators. It started with the people these products claim to serve.

The National Federation of the Blind passed a resolution opposing overlays in 2021 and revoked accessiBe’s sponsorship of its national convention, stating that the company “currently engages in behavior that is harmful to the advancement of blind people in society.” That is a striking thing for an advocacy organization to say about a company selling accessibility.

There is also a long-running open letter in the field, the Overlay Fact Sheet, signed by a large number of accessibility practitioners and developers who commit to not recommending overlay products. I am deliberately not quoting a signature count here, because the numbers circulating online vary and I could not confirm a current figure from the source itself. The document is easy to find and reads for itself.

Does an overlay protect you legally?

I am not a lawyer, and here I want to be careful in a way the marketing on both sides of this argument usually is not.

You will find claims that hundreds of businesses running overlays have been sued anyway. Those figures generally trace back to companies selling competing accessibility services, and I could not verify them against a neutral source, so I am not going to hand you a number I cannot stand behind.

What I can say rests on plainer logic. A demand letter is typically built on specific failures against WCAG: this image lacks alt text, this form field lacks a label, this contrast ratio falls short. If the underlying markup still contains those failures, installing a widget on top of it has not removed the thing the complaint is about. Whatever the exact litigation statistics turn out to be, that is the mechanism, and it does not depend on anyone’s marketing.

If you already have one

Do not panic, and do not necessarily rip it out this afternoon.

Find out where your site actually stands first. Run the free checklist with the widget switched off and see what is underneath it. That tells you whether you have been paying a monthly fee to cover a small problem or a large one.

Then fix the real issues in the code. Once the markup is right, the toolbar features become optional, which is the correct relationship to have with them. It is worth doing the arithmetic at that point: an overlay subscription is a permanent monthly cost, while remediation is a one-time one. Over a few years the widget frequently turns out to be the more expensive way to not solve the problem.

My work goes into the source: structure, keyboard operation, contrast, focus, labels and alt text, verified against WCAG 2.2 AA with a written summary of what was tested. Here is what that audit involves, the wider legal context is in ADA website compliance, what it actually means, and the service itself is on the ADA compliance page.

If you are weighing a renewal against doing it properly, book a free 30-minute call and I will tell you which one I would do in your position. If the honest answer is that your site is mostly fine already, that is what I will say.