Accessibility overlays: why a widget does not make you compliant

An accessibility overlay is a JavaScript snippet that adds a floating “accessibility” button and promises WCAG, EAA or ADA compliance in one line of code. It is the most heavily marketed product in the category — and the one the disability community, accessibility professionals and increasingly regulators warn against. Here is why, with the evidence, and what to do instead.

What overlays actually do

• Inject a toolbar for font size, contrast themes, cursor size and text spacing — functions that browsers, operating systems and assistive technologies already provide, often better.
• Attempt runtime “repairs”: guessing alt text with image recognition, adding ARIA attributes, re-ordering focus. These guesses are frequently wrong and can make a page less usable for screen-reader users.
• Leave your HTML, CSS and templates exactly as broken as before. Turn the script off and every issue is back.

Why they fail the standard

• WCAG is about the content and code your site delivers. A widget cannot fix missing form labels in a meaningful way, cannot write accurate alt text for your product photos, cannot repair a keyboard trap in your checkout, and cannot make a PDF accessible.
• Automated scanners still report the underlying violations because they test the DOM your site ships — which is also what an auditor or an expert witness will test.
• Many overlays are themselves not keyboard-accessible or interfere with the user's own assistive technology settings.

What the community and regulators say

• The Overlay Fact Sheet, signed by hundreds of accessibility practitioners and disabled users, states that overlays do not achieve conformance and asks vendors to stop the compliance claims.
• In January 2025 the US Federal Trade Commission announced an order against overlay vendor accessiBe over claims that its widget could make any website WCAG compliant, including a $1 million payment — treating the compliance promise as deceptive advertising.
• Screen-reader users have filed complaints and many block overlay scripts outright with browser extensions.

Why they do not stop lawsuits or fines

• Hundreds of US ADA lawsuits every year name websites that had an overlay installed. Plaintiffs' experts simply disable the widget and audit the code.
• Under the EAA and BFSG, authorities assess conformity with EN 301 549 and your documentation. “We installed a widget” is not a conformity assessment.

What to do instead

• Find the real issues: run a WCAG 2.1/2.2 AA scan in a real browser; you get each failing element with its selector and the users it affects.
• Fix the source: apply corrections in your templates and components — generated fixes give you a reviewed starting point for contrast values, labels, ARIA roles and alt attributes.
• Verify by re-scanning and by manual keyboard and screen-reader checks.
• Document: keep dated reports and publish an honest accessibility statement.
• Monitor every release via the Scan API or a scheduled scan.

This is exactly why FixRamp does not offer an overlay and never will: fixing code is more work than pasting a script, but it is the only thing that makes your site usable — and defensible. General information, not legal advice.