Account

What new tool do you want?

Web & SEO

Accessibility Overlay Checker

Check whether a website uses an accessibility overlay widget (accessiBe, UserWay, AudioEye, EqualWeb and others) — and learn why overlays don't make sites accessible.

How to use

  1. 1Enter a website.
  2. 2See whether an overlay is installed and what to do instead.

Frequently asked questions

What is an accessibility overlay?

A script that adds a toolbar or automated “fixes” on top of a website instead of fixing the site's code.

Are overlays bad?

Many disabled users and accessibility experts say overlays don't fix real barriers and can interfere with assistive technology; over 1,000 accessibility professionals have signed the Overlay Fact Sheet.

What should I do instead?

Fix issues at the source — alt text, form labels, color contrast, keyboard navigation and headings — and test with real assistive technology.

Why an overlay and a genuine accessibility fix look completely different under the hood

A real accessibility fix changes the underlying HTML itself — adding a proper alt attribute to an image, associating a label with a form field, fixing heading order in the markup — permanently improving what every visitor's browser and assistive technology receives. An overlay instead injects a separate script that layers a floating toolbar and attempts automated, generic adjustments on top of the existing page at runtime, without touching the actual source code — which is exactly the distinction this checker is built to detect: is there an overlay script present, as opposed to whether the site's actual markup is accessible (a separate question the companion Accessibility Checker tool addresses).

Worked example: Accessibility Overlay Checker

Checking a site and finding a known overlay script (say, from accessiBe, UserWay, AudioEye or EqualWeb) loaded in the page tells you the site owner has installed a widget — commonly a visible accessibility icon in a corner of the page — but says nothing about whether the site's actual code has been fixed. A site with no detected overlay at all might still have excellent native accessibility if it was built with proper semantic HTML and labels from the start, while a site with an overlay installed could still have all its underlying structural problems completely intact underneath the widget.

Why over a thousand accessibility professionals have taken a public position on this

The FAQ's reference to the Overlay Fact Sheet isn't a one-off opinion — it points to a substantial, organized consensus among disabled users and accessibility practitioners that overlays frequently fail to address real barriers and can actively interfere with the assistive technology (screen readers, voice control, browser extensions) that disabled users already rely on and have configured to their own needs. An overlay script intercepting and modifying page behavior can conflict with a screen reader's own navigation model, sometimes making a page harder to use than if no overlay were present at all.

What finding (or not finding) an overlay tells you to do next

Detecting an overlay is a prompt to look deeper, not a verdict either way — it means checking whether the site's actual code has also been fixed (an overlay alone, per the consensus above, usually isn't sufficient), while the absence of an overlay doesn't confirm good accessibility either, since the site might simply not have addressed accessibility through any method yet. Either result points to the same next step: testing the real markup and interactive behavior directly, using a scanner, a keyboard, and ideally real assistive technology, rather than relying on the presence or absence of a widget as a proxy for whether the site actually works for disabled visitors.

Related tools

More: Web & SEO