The pitch is close to irresistible when you are the person who has to say no to it. One script tag. A floating icon in the corner. Compliance handled by Thursday, at a fraction of what an audit costs, with no engineering time and no sprint negotiation.
I have lost this argument in meetings and I have won it, and the difference was never how strongly I felt about it. It was whether I could explain concretely what the widget does and does not touch. So here is that explanation, in the form I wish I had the first time.
What an overlay actually does
An overlay is JavaScript that runs after your page loads and modifies it. It generally does two separate things that get marketed as one.
The first is a user preference panel. Increase font size, raise contrast, underline links, stop animations, adjust letter spacing. This part is real and it works. It is also, almost entirely, functionality the operating system and browser already provide, better, and system wide.
The second is automated remediation. The script scans the DOM and tries to patch what it finds: guessing alternative text from filenames or image analysis, inferring labels for unlabeled inputs, injecting ARIA roles onto elements that look like they should have them.
That second part is where the claim lives and where it falls apart.
Why automated remediation cannot close the gap
The European Commission has stated that no automated tool covers the full set of WCAG 2.1 AA criteria. That is not a criticism of any particular vendor, it is a statement about the nature of the criteria.
A large share of WCAG is about meaning, and meaning is not recoverable from markup. Consider a few concrete cases.
- Alternative text requires knowing the image’s purpose in context. The same product photo needs different alt text on a category grid, a product page, and a decorative banner. A script cannot know which one it is looking at, and generated descriptions of a chart rarely convey what the chart is arguing.
- Keyboard navigation depends on your event handlers, your focus management, and your DOM order. An overlay cannot rewrite a click handler bound to a div into a real button with correct activation behaviour, and it cannot repair a focus trap in a modal it did not build.
- Heading structure reflects document meaning. A script can see that you have an h4 followed by an h2. It cannot know which one was wrong.
- Error identification in forms requires knowing what the error means and where the user should go. Injecting a generic role does not produce a useful message.
Industry estimates put the share of WCAG issues that automated tooling can even detect at somewhere between a quarter and a third. Detection is a lower bar than repair. So the ceiling on what a script can fix is well below the ceiling on what it can find, and the ceiling on what it can find is already well below the standard.
The part that makes it worse rather than neutral
If an overlay were simply ineffective, it would be a waste of budget and nothing more. The reason it draws stronger objections than that is interference.
Screen reader users arrive with their own assistive technology, configured to their preferences, which they know intimately. An overlay that injects its own keyboard shortcuts, its own reading interface, or its own ARIA can collide with that setup. Advocacy organisations have been vocal about this for years, and a substantial number of screen reader users report actively working around overlay sites rather than being helped by them.
There is also a diagnostic cost. Once a script is rewriting your DOM at runtime, your own testing becomes unreliable. You cannot tell whether a passing check reflects your markup or the patch sitting on top of it, and the patch does not ship with your codebase.
The legal position has moved
This is the argument that tends to land with people who were unmoved by everything above.
The largest overlay vendor was reportedly fined one million dollars by the US Federal Trade Commission over its marketing claims. Hundreds of sites running overlays have been sued anyway, which is the practical answer to the question of whether the widget provides cover. And in EU enforcement contexts the presence of an overlay has begun to read to authorities as an indicator that the underlying site was never remediated, because a company that fixed its markup would not need one.
The documentation problem is the quiet one. Under the European Accessibility Act you may be asked for a conformance report and an accessibility statement grounded in real testing. A widget does not generate either. It cannot tell you which criteria you meet, because it does not know.
What to say when it comes up
The framing that works, in my experience, is cost of ownership rather than ethics. Ethics arguments make the person proposing the overlay feel accused, and then the conversation is about them.
Try this instead. An overlay is a recurring annual subscription that does not reduce your exposure, does not produce your documentation, and leaves the same remediation work in the backlog it was purchased to avoid. In three years you will have paid three subscriptions and still owe the audit. The overlay is not cheaper than fixing the site. It is a payment plan on not fixing it.
What to do with that budget instead
- Fix the template level failures first. Contrast, alt text, form labels, empty links and buttons, document language. These live in a handful of components and account for the overwhelming majority of detected errors across the web.
- Put axe-core in CI and fail the build on new violations. This costs an afternoon and it stops the problem from regrowing while you work through history.
- Run one manual keyboard pass per release on your highest value flow. Twenty minutes, no tooling, finds the blocking issues automation structurally cannot.
- Test with a real screen reader on that same flow. NVDA on Windows, VoiceOver on macOS. Both free, both already installed on someone’s machine.
- Write the accessibility statement from findings. Known gaps and a remediation timeline read as good faith. A blanket conformance claim that a five minute test contradicts reads as the opposite.
None of that is glamorous and none of it fits in an afternoon. It is, however, the only version that is still true a year later.
I am an engineer, not a lawyer. Enforcement details and penalty figures vary by jurisdiction and change over time. Get local counsel for your specific situation.
I audit and remediate ecommerce frontends against WCAG 2.1 and 2.2 AA. If someone on your team is currently pricing an overlay, write to me first at serbeldiaz@gmail.com.
No responses yet