Accessibility Overlays vs. Real Fixes: Why a Plugin Cannot Make Your Site Compliant

The badge that didn't stop the letter

A clinic installed an accessibility overlay on its site in 2022. It added the floating icon, the contrast toggles, the generated accessibility statement, and a compliance badge in the footer. It cost a few hundred dollars a year and took about twenty minutes.

Eighteen months later, a demand letter arrived alleging that the site was inaccessible because a screen reader could not complete the appointment booking form.

The overlay was still installed. It had been working the entire time. It had simply never had anything to do with the booking form, which was a third-party widget the overlay could not reach.

That story is the whole overlay problem in miniature, and it's why the products are now the most contested topic in web accessibility.

What an overlay is, fairly described

A script that changes how a page is presented. It adds a floating button, and behind that button are preferences: bigger text, higher contrast, a dyslexia-friendly font, spacing adjustments, link highlighting.

Used honestly, that's a legitimate feature. Some visitors with low vision, light sensitivity, or reading difficulties genuinely benefit, and a visible tool saves them hunting through browser settings.

The problem isn't the feature. It's the marketing claim wrapped around it, and what that claim persuades a business to stop doing.

What it cannot do

The barriers that actually exclude people are structural, and a script injected at the end of the page load cannot rewrite structure it doesn't control.

• Keyboard order and focus. If a field can't be reached with Tab, or focus vanishes when a menu opens, no overlay invents a logical path the markup never had.
• Missing form labels. A placeholder that disappears on typing leaves a screen reader user with an unnamed field. The fix is markup.
• Link text. Links announced as "click here" are ambiguous in a screen reader's link list. Only editing the content fixes that.
• Heading structure. Headings chosen for their size break the page outline. An overlay can't reliably reorder the reading sequence.
• Image alternatives. A description has to be written by someone who knows what the image shows. Auto-generated text is frequently useless, and sometimes actively wrong.
• Third-party embeds. Booking tools, review carousels, payment frames, map widgets, chat windows. They live outside your page and completely outside the overlay's reach. This is the one that most often causes a claim, because it's exactly where the transaction happens.
• Documents. PDFs, menus, price lists, application forms. A large share of real barriers sit here and overlays never touch them.
• Content added after load. Dynamically rendered elements can bypass the layer entirely.

And there's a measurement trap underneath all of it. Overlays detect problems the way automated scanners do, and the long-running WebAIM Million analysis of home pages keeps finding the same thing: automated testing catches only a fraction of real accessibility issues. A clean scan has never been evidence of an accessible site.

The regulatory turn, which changed the argument

For years, the objection to overlays was principled: accessibility practitioners said they didn't work, vendors said they did, and businesses bought them because they were cheap and fast.

Then it stopped being a debate about effectiveness.

In January 2025, the US Federal Trade Commission settled with accessiBe, one of the largest overlay vendors, for one million dollars over allegations that its marketing overstated what its automated widget could achieve, including claims that customers could become compliant within days and testimonials presented as independent. The FTC's position was that the compliance promise itself was deceptive.

Whatever you think of specific vendors, the practical consequence is now clear: "install this and you're compliant" is a marketing claim with legal exposure of its own, and it does not answer the question a court or a complainant asks, which is whether the website is accessible.

Major disability organisations, including the National Federation of the Blind in the US, have criticised these products for years on the same grounds: they claim a compliance they cannot deliver and divert effort from real fixes.

What an overlay is legitimately good for

Worth being specific, because "overlays are bad" is as lazy as "overlays solve compliance".

Useful, if you already have an accessible site:

• Reader preferences. Larger text, letter spacing, contrast modes. Real value for some visitors.
• A visible statement of intent, if it links to a genuine accessibility page with a contact route.
• Highlighting structure: outline links and headings so a sighted keyboard user can orient.

Not useful:

• Legal protection.
• Replacing markup fixes.
• Covering a third-party component you haven't checked.

The rule I'd apply: an overlay is a nice optional layer on top of an accessible site, and never the site's accessibility.

What actually fixes it

Real remediation is layered, and each layer catches what the previous one missed.

1. Automated scan for a baseline

Tools like axe, Lighthouse, and WAVE find the mechanical failures fast: missing labels, contrast ratios, missing page language, duplicate IDs. Run them against templates rather than pages, because templates repeat, and a broken footer is one fix, not four hundred.

Automated scanning is good at finding problems and hopeless at judging usability. Treat its output as a list of things to check, not a verdict.

2. Keyboard-only pass

Put the mouse away. Tab through your booking flow, your contact form, and your checkout. Can you reach everything? Can you see where you are? Does focus get trapped in a modal? Does the sticky header cover the field you're typing into?

This catches the failures that cause claims, and it takes twenty minutes.

3. Screen reader pass on the money flow

VoiceOver on a phone, or NVDA on Windows. Close your eyes and try to book something. You'll discover what the automated scan couldn't: that the form reads as "edit text, edit text, edit text" with no indication of what's wanted.

4. Fix the components, not the instances

Forms, modals, menus, tables, carousels. Build each once, properly, and reuse. Nine times out of ten the accessibility problem is one component used on thirty pages, which means one fix produces thirty improvements.

5. Deal with the third parties

Your booking widget, payment provider, and chat tool are part of your site from a user's perspective. Ask vendors for their Accessibility Conformance Report, and check the flow yourself. Where a vendor won't engage, offer an accessible alternative route: a phone number, a plain HTML form that emails you, a documented process.

6. Publish a real accessibility statement

Not the auto-generated one. Your target standard, known limitations with dates, how to report a problem, and who replies. It won't protect you on its own, but it's the difference between a business that thought about this and one that didn't, and it gives a frustrated visitor a route that isn't a lawyer.

How to evaluate a vendor's claim

If you're being sold an overlay, four questions:

1. Which specific success criteria does the tool fix, and which does it not? A written list. If the answer is "all of them", that's the answer.
2. What happens with third-party widgets and PDFs? The most likely location of your real problem.
3. Can I see the Accessibility Conformance Report, and is it for the tool or for my site? A vendor report isn't an audit of your website.
4. If I stop paying, what happens to my accessibility? With an overlay, it reverts entirely. With remediation, it stays fixed.

The fourth question is the one that clarifies the whole category.

Where to start

Turn the overlay off for an afternoon and try to book your own service with a keyboard, then with a screen reader on a phone. Everything you hit is what the overlay was covering, and everything you hit is fixable.

A free digital presence audit on Webcheckhub includes accessibility basics in website health, which shows whether the problems are concentrated in one component or spread across the site. When you want the remediation done properly, with a documented audit and the fixes implemented in the code, Solutions Elites handles accessibility work for small businesses.