Why Accessibility Overlays Don't Work (And What to Do Instead)

Accessibility overlays — JavaScript widgets that promise to make websites WCAG-compliant with a single line of code — have become one of the most controversial products in the web accessibility space. In April 2025, the FTC fined overlay provider accessiBe $1 million for making false compliance claims. This ruling validated what accessibility professionals have been saying for years: overlays do not work.

What are accessibility overlays?

Overlays are third-party JavaScript widgets that inject a toolbar or menu onto a website. They typically offer features like text resizing, colour contrast adjustments, and screen reader "optimization." The marketing pitch is compelling: add one script tag and your website becomes accessible. No code changes needed.

The reality is very different.

Why overlays fail

1. They cannot fix structural HTML problems

Most WCAG violations are in the HTML source code — missing alt attributes, incorrect heading hierarchy, unlabeled form fields, missing ARIA roles. An overlay script running in the browser cannot rewrite the DOM in a way that reliably fixes these issues. It can add attributes dynamically, but this approach is fragile, often breaks existing functionality, and frequently introduces new accessibility barriers.

2. They interfere with assistive technology

Screen reader users overwhelmingly reject overlays. A 2023 survey by WebAIM found that over 67% of screen reader users reported that overlays made websites harder, not easier, to use. The dynamic DOM changes conflict with how screen readers parse and present content, creating a worse experience than the original inaccessible page.

3. They create a false sense of compliance

The biggest danger of overlays is that they convince site owners they have "solved" accessibility when they have not. This delays genuine remediation efforts and leaves organizations exposed to legal risk. The EAA, ADA, and other regulations require the underlying website to be accessible — not just that a widget is installed.

4. They are a litigation target

According to UsableNet, 22.6% of accessibility lawsuits in 2025 targeted websites using overlay widgets. Rather than preventing litigation, overlays appear to attract it — plaintiffs and their attorneys view overlay-equipped sites as low-hanging fruit because the underlying violations remain.

The FTC ruling

In April 2025, the Federal Trade Commission fined accessiBe $1 million and required the company to stop claiming that its widget makes websites ADA or WCAG compliant. The FTC found that accessiBe's marketing was deceptive because the overlay did not, in fact, make websites accessible. This is a landmark ruling that puts all overlay providers on notice.

What actually works

There is no shortcut to web accessibility. Here is what the evidence shows:

1. Fix your source code. Accessibility must be built into your HTML, CSS, and JavaScript. Add proper alt text, use semantic HTML elements, ensure keyboard navigation works, implement ARIA correctly where needed.
2. Use automated scanning to find issues. Tools like axe-core can identify approximately 57% of WCAG violations automatically — the most common and impactful ones. This is your baseline.
3. Conduct manual testing. Tab through your site with a keyboard. Test with a screen reader (NVDA is free on Windows, VoiceOver is built into macOS). Ask real users with disabilities to test your flows.
4. Monitor continuously. Accessibility is not a one-time fix. Every code deploy, content update, or plugin change can introduce new issues. Automated monitoring catches regressions before users encounter them.
5. Train your team. Developers, designers, and content creators all play a role. Accessibility knowledge should be embedded in your development process, not bolted on at the end.

The path to real accessibility requires more effort than installing a widget, but it produces results that actually work — for your users, for compliance, and for your business.