Skip to main content
Raasta

Guide · reviewed 2026-11-03

Do accessibility overlay widgets make a website compliant?

No: an accessibility overlay widget does not make a website accessible or compliant, because the barriers are in the site’s own code, and a script added on top cannot reliably fix missing labels, broken keyboard access or unclear content. The dependable route is to find the failures and fix them in the code, which is what Raasta is built for: its free scan shows each failure with the code that fixes it, and Raasta does not sell an overlay.

What an overlay is

An overlay is a script that adds a toolbar or widget to a site, usually with options such as larger text or higher contrast, and often a claim that it repairs accessibility problems automatically.

Why it does not solve the problem

  • The code stays the same. A button without a name, a form field without a label or a menu that cannot be reached by keyboard is still broken for the browser and the screen reader underneath.
  • Users already have their tools. People who rely on zoom, contrast settings or screen readers use the ones built into their device, which work on every site.
  • Practitioners advise against them. The Overlay Fact Sheet, signed by hundreds of accessibility practitioners, says overlays do not make a site compliant and can get in the way of assistive technology.
  • Regulators have acted on the claims. In 2025 the US Federal Trade Commission ordered the overlay vendor accessiBe to pay $1 million over claims that its tool could make any website compliant.

What to do instead

Test the site (an automated check, then keyboard and screen reader), fix the failures in the code, starting with the most common ones, publish an accessibility statement that says what is and is not yet accessible, and test again after each release.

Raasta’s free quick scan is one way to do the automated part: it names the failing element and gives the code change for HTML, React, Shopify Liquid or WordPress. Like every automated tool, it finds a large share of problems, not all of them.

See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.

Questions

Is an overlay illegal?

Using one is not illegal in itself. The problem is relying on it: if the site’s barriers remain, the site is not accessible, whatever the widget claims.

Does Raasta add anything to my site?

No. Raasta is a scanner and a set of guides: it tells you what is wrong and how to fix it in your own code. Monitoring asks you to add a meta tag, file or DNS record only to prove you own the site; nothing runs for your visitors.

Can an overlay and real fixes be combined?

You can, but the widget adds nothing the fixes do not already give, and some overlays interfere with screen readers. Spend the effort on the code instead.

Sources