Does your accessibility overlay actually fix anything?

Enter your address. We will tell you whether an overlay is installed, quote the evidence from your own source, and then show you the WCAG failures that are still in your markup either way. Free, no signup.

What an overlay is, in one paragraph

An accessibility overlay is a script you add to your site. It loads a floating button, and behind that button a panel of adjustments: bigger text, more contrast, wider spacing, sometimes a screen-reader mode. Some products also try to repair missing information as the page loads, guessing image descriptions or form labels. All of it happens in the visitor browser, after your server has already sent the page.

That single fact is the whole of it. The adjustments are real, and some visitors value them. The repairs are guesses layered on top of markup that still contains the original problem.

Products this checker recognises

We look for the loader scripts of these products. Naming them is not a criticism of any of them. It is how we tell you, factually, what is on your page.

Common questions

Do accessibility overlays work?
They do some real things. An overlay can offer a visitor larger text, higher contrast, more spacing, or a reading guide, and some people genuinely use those controls. What an overlay cannot do is change the HTML your server sent. If an image has no alternative text, a form field has no label, or your headings are out of order, those failures are still in your source after the overlay loads.
Will an overlay make my site WCAG compliant?
No automated tool of any kind can establish compliance, and that includes ours. Conformance is judged against your delivered pages and confirmed by manual testing with real assistive technology. An overlay runs after delivery, usually only once a visitor opens the widget and chooses a setting, so it does not change what an auditor examines.
Are accessibility overlays legal to use?
Installing one is not against any law, and this page is not legal advice. The practical point is narrower and technical: an overlay does not by itself demonstrate that your pages meet a standard, because the failures it leaves in your markup are the ones a reviewer looks at. If you need a legal position, ask a lawyer.
What are the main problems with accessibility overlays?
Three that follow from how they work. They depend on JavaScript, so a blocked or failed script leaves the original page. They guess at missing information such as image descriptions and form labels, and a wrong guess can be more misleading than an absence. And they do not edit your source, so the underlying defects persist for anyone who is not using the widget.
How does this checker find an overlay?
It reads the HTML your page delivers and looks for the loader script of known overlay products, then quotes the matching source back to you so you can confirm it by viewing source yourself. If an overlay is injected later by a tag manager, it will not appear in the delivered HTML, so a negative result means we did not find one rather than that none exists.

Nothing here is legal advice. See our disclaimer.