An overlay is not compliance. See what it left broken.
Accessibility overlays promise conformance from the outside and deliver a lawsuit magnet instead. This names the overlay on your page and lists the failures it did not fix: the ones a plaintiff's tester finds in thirty seconds.
How the overlay check recognises a widget, and what the score beside it tells you.
Our server fetches the address and reads the HTML source without running it in a browser. It compares every src and href in the markup with script addresses used by seven overlay vendors: accessiBe, UserWay, EqualWeb, AudioEye, AccessiWay, Recite Me and Allyable. In the same pass it runs 13 source-level accessibility checks, covering page language, title, heading structure, image alt attributes, form labels, link text, tabindex, the main landmark, viewport settings and table headers, and turns the findings into a score out of 100. Finding an overlay never changes that score. An email, if added, is saved with the page address and the verdict.
No overlay means none of those vendor addresses appears in the source. Once an overlay is named, a single threshold decides the verdict: a score below 90 gives Overlay - still failing, and 90 or above gives Overlay - liability. The list beneath shows up to eight finding types, most severe first, each with the WCAG success criterion it relates to. These are faults in the markup as the server delivered it, before any widget script has run. The same list is shown when no overlay is found, and then it is just the result of the source checks.
Because nothing is rendered, the check does not execute the overlay and cannot show what the widget changes in the browser; the findings describe the page as served. An overlay loaded through a tag manager, or from a vendor outside the list, is not named. Colour contrast, focus order and keyboard behaviour are not measured. If an overlay is named, the useful next step is a manual test with a keyboard and a screen reader, once with the widget active and once with it blocked, followed by fixes in the markup itself.
- What is an accessibility overlay?
- An accessibility overlay is a third-party script added to a website, usually with one line of code. It typically shows a floating button that opens a toolbar for changing contrast, text size or spacing, and some products also try to repair the page automatically in the browser, for example by generating image descriptions or adding ARIA attributes. The site's own source code stays as it was.
- Does an accessibility overlay make a website WCAG compliant?
- Not by itself. Many WCAG criteria need human judgement: whether an image description is meaningful, whether the focus order makes sense, whether a custom component can be operated with a keyboard. Automated repair in the browser cannot settle those, and it only works for visitors whose assistive technology cooperates with the script. Accessibility practitioners generally advise fixing the source code and testing with real assistive technology.
- How can I tell whether a website uses an accessibility overlay?
- Look for a floating accessibility button, usually in a corner of the page. To be sure, open the page source or the network tab of the browser's developer tools and search for script addresses belonging to overlay vendors. A widget injected through a tag manager shows up only in the network tab, not in the source, because it is added after the page has loaded.
When one check is not the whole job.
Running one? The honest fix is conformance in the markup, with proof.
