By Mehdi HassanDo accessibility overlays work?
No, accessibility overlays don't work as a way to make a website accessible or compliant. They can change some visual settings, like text size or contrast, but they can't reliably repair the code that keyboards and screen readers depend on. Our view is blunt because the evidence is: if your site has real barriers, an overlay leaves them in place and adds a toolbar on top.
This matters because overlays are sold as the fast, cheap answer to legal risk, and many of the pages that rank for accessibility questions are written by companies that sell them. We don't sell widgets or scanners. We design and build websites, and we fix accessibility in the code. The full legal background is in our hub on website accessibility compliance.
If a button has no label in the code, no widget can know what that button does.
What is an accessibility overlay?
An accessibility overlay is a third-party script that adds a toolbar or automated layer to your website, promising to improve accessibility without changing your code. You paste one line of JavaScript, and an icon appears in the corner. Most are sold as a monthly subscription.
There are two parts to most overlay products. The visible accessibility widget lets visitors change text size, spacing, contrast or cursor size. The invisible part claims to scan the page and fix problems automatically, often described as AI: adding alt text, labeling buttons and adjusting markup as the page loads. Some accessibility plugins for CMS platforms work the same way.
The visible toolbar duplicates what browsers and operating systems already do: zoom, high-contrast modes, reader view and screen readers. The invisible repair layer is the part that's sold as compliance, and it's the part that falls short.
What did the FTC's accessiBe case find?
The US Federal Trade Commission alleged that accessiBe misrepresented what its AI-powered overlay could do, including claims that it could make any website compliant with WCAG. The FTC also took issue with how reviews of the product were presented. The order, finalized in April 2025, requires accessiBe to pay $1 million and bars it from making unsupported claims about its product.
- FTC order against accessiBe, finalized April 2025
- $1M
- Federal website accessibility suits in 2025 (Seyfarth)
- 3,117
The case was about advertising claims, not a ruling on accessibility law. But it's the clearest public statement from a US regulator that 'install this and you're compliant' isn't something a vendor can promise. Accessibility practitioners had said the same for years; the FTC order put it on the record.
What the FTC case does not say
The order doesn't ban overlays, and it doesn't say that every overlay product is useless for every visitor. It deals with one company's marketing claims.
It also doesn't change your own obligations. Under the ADA and the European Accessibility Act, the business running the site is responsible for its accessibility. Paying a vendor doesn't transfer that responsibility, whatever the vendor's sales page says.
Why can't an overlay fix accessibility problems?
An overlay can't fix accessibility because most barriers come from missing meaning in the code, and meaning can't be guessed reliably by a script. A screen reader announces what the HTML says. If a checkout button is a styled div with no name, the overlay has to infer what it does. Sometimes it guesses right; sometimes it labels 'Pay now' as 'button'.
Problem | Can an overlay fix it? | Real fix |
|---|---|---|
Low text contrast | Partly, if the user turns on a mode | Change the colors in the design system |
Missing alt text | Guesses, often vague or wrong | Write alt text that says what matters |
Unlabeled form fields | Unreliable | Visible labels in the HTML |
Keyboard traps in modals | Rarely | Fix focus handling in the component |
Wrong focus order | No | Fix the DOM order and layout |
Custom controls without roles | Unreliable | Use native elements or proper ARIA |
Unclear error messages | No | Rewrite the copy and announce errors |
Inaccessible third-party embeds | No | Replace or fix the embed |
There's a second problem. Many disabled users already have assistive technology set up the way they like it. An overlay that changes page behavior can conflict with their screen reader or browser settings, which is why some users install tools specifically to block overlays.
Does an accessibility widget protect you from lawsuits?
No. An accessibility widget doesn't protect you from ADA lawsuits, and businesses with overlays installed continue to be sued. Plaintiffs test whether they can complete tasks on your site; if the checkout still can't be used with a screen reader, the toolbar in the corner doesn't change that. Seyfarth counted 3,117 federal website accessibility suits in 2025, and overlay users aren't exempt from that pipeline.
The same goes for the EU. Under the European Accessibility Act, national authorities assess whether the service meets the requirements, using EN 301 549 and WCAG AA. Nothing in the directive treats a third-party widget as conformance. And in the US, as our guide to ADA website compliance explains, courts and settlements look at WCAG AA in the site itself.
Is there anything overlays get right?
To be fair, overlays do a few small things that some visitors find helpful, and the underlying need they sell to is real: businesses want accessibility to be easy. The problem is that easy isn't on offer for the hard parts.
Pros
- Cheap and fast to install compared with remediation
- Text-size and spacing controls can help some users who don't know their browser settings
- Some products include scanning that can flag issues for your team to fix
Cons
- Doesn't fix missing labels, focus order or markup reliably
- Can conflict with screen readers and user settings
- Not accepted as compliance by courts or regulators
- Monthly cost that never ends, while the site stays broken underneath
- Adds a third-party script that can slow the page
What should you do instead of an accessibility overlay?
Instead of an overlay, fix the shared parts of your site in code and design, then keep them fixed. On most marketing sites, a handful of components cause most of the issues, so the work is smaller than a long scan report suggests.
Test your key flows
Run a free scanner, then complete signup, checkout or booking using only a keyboard and then a screen reader.
Fix components, not pages
Repair buttons, links, forms, navigation and modals once in the component library, so every page gets the fix.
Fix the brand palette
If contrast fails everywhere, adjust colors in the design system. Our guide to accessible design basics shows how to keep the look.
Write the missing words
Alt text, labels, link text and error messages are copy work, not code magic.
Check against WCAG 2.2 AA
Use our WCAG 2.2 checklist to confirm each item, and consider a manual audit if the stakes are high. See accessibility audit cost.
Remove the overlay
Once the site is fixed, the widget adds nothing but a script and a subscription.
