Key takeaways
- An accessibility overlay is a single script that promises automatic compliance. It cannot deliver it, because automated tooling only addresses a fraction of WCAG.
- More than 1,000 accessibility professionals have signed a public statement that overlays are unreliable and cannot achieve compliance.
- The FTC fined accessiBe $1,000,000 in 2025 for claiming its widget could make any site WCAG-compliant.
- Sites that install overlays still get sued. Roughly 1 in 4 US ADA web lawsuits in 2024 named a site that already had a widget running.
- The only fix that holds up legally is changing the underlying theme code. Find the issues, fix them at the source, and monitor for regressions.
If you have looked into Shopify accessibility, you have seen the pitch: install one line of code and your store becomes ADA and WCAG compliant overnight. The tools making that promise are called accessibility overlays, and the products include accessiBe, UserWay, AudioEye, and Accessibly.
The promise is appealing and the reality does not match it. Overlays do not make a store compliant, the accessibility community has rejected them, regulators have penalized them, and stores that use them still get sued. Here is what is actually going on, and what to do instead.
Why you can trust us
Jacques has over 15 years of development experience building accessible storefronts, and we have spent over four years in the Shopify ecosystem. We built Fudge, an AI store builder with a 5.0 rating on the Shopify App Store that fixes accessibility issues in native theme code. We have no overlay product to sell you, and our view matches the consensus of the accessibility engineering community, which we cite throughout.
What is an accessibility overlay?
An accessibility overlay is third-party JavaScript you add to your store. It loads on top of your existing pages and typically does two things: it shows a floating accessibility menu (font size, contrast toggles, and similar widgets), and it claims to automatically detect and repair accessibility problems in the background.
The marketing positions a single script as full compliance. The technical reality is that the script runs on top of your HTML without changing the HTML underneath.
Why overlays cannot make you compliant
The core problem is structural. An overlay is automated code reacting to your page after it loads. It cannot understand context the way a person can, and it cannot rewrite the source of the problems.
Automated tools only catch part of the picture. Independent testing consistently shows that automated detection covers roughly 30 to 40% of WCAG success criteria. The rest, including whether alt text is meaningful, whether the keyboard order makes sense, and whether a screen reader can complete checkout, requires human judgment. An overlay cannot supply that judgment.
The experts who build accessibility have rejected overlays. More than 1,000 accessibility professionals, including people who contributed to the WCAG guidelines themselves and engineers behind major screen readers, have signed the Overlay Fact Sheet, which states plainly that overlays are unreliable and cannot achieve compliance.1 The National Federation of the Blind has condemned them, and in WebAIM’s survey a large majority of practitioners and disabled users reported overlays were ineffective.
Overlays can make the experience worse. For some screen-reader and keyboard users, the overlay interferes with the assistive technology they already use, creating new barriers rather than removing them.
The legal reality: overlays do not stop lawsuits
This is the part that surprises store owners most. Installing an overlay does not protect you, and in one notable case the vendor itself was penalized.
The FTC fined accessiBe $1,000,000. In 2025 the Federal Trade Commission finalized a $1,000,000 order against accessiBe for deceptively claiming its accessWidget product could make any website WCAG compliant, and for presenting paid reviews as independent.2 The order bars those compliance claims.
Sites with overlays still get sued. Roughly 1 in 4 of the more than 4,000 US ADA web accessibility lawsuits filed in 2024 named a site that already had an accessibility widget or overlay installed.3 In the well-known Murphy v. Eyebobs case, a blind plaintiff sued a store that was running an overlay and the case settled. Overlay vendors’ own terms of service often concede that installing the product does not by itself satisfy the law.
The takeaway: an overlay is a recurring subscription that gives you a false sense of safety while the underlying issues, and the legal exposure, remain.
The privacy angle
Overlays often process information about how visitors interact with your site, and some attempt to detect assistive technology use. That raises privacy questions, since assistive-technology use can reveal a disability. The Overlay Fact Sheet flags this as one of the recurring concerns with the category.1
What actually works: fix the code
Every durable accessibility fix is a change to the underlying theme code. That is the part overlays skip, and it is the only part that holds up legally.
The model we recommend, and the one we built Fudge around, has three steps:
- Surface what needs fixing. Scan the store to find the real issues in your theme, from low-contrast text to missing labels and alt text. For the full method, see our guide on Shopify ADA and WCAG compliance.
- Fix it in native code. Repair the issues directly in your Liquid, CSS, and JavaScript so the page itself is accessible, not masked by a script. This is what a developer would do, and what courts and regulators recognize.
- Monitor for regressions. Accessibility is not one-and-done. A future theme update or content edit can reintroduce a failure, so keep checking.
The difference is fundamental. An overlay sits on top of broken HTML and you re-buy it every month. Fixing the code removes the problem, improves the experience for real users, and stays fixed.
How to move off an overlay
If you already run one, the transition is straightforward:
- Run an honest audit of the store with the overlay disabled, using a free tool like axe DevTools or WAVE plus a manual keyboard and screen-reader pass.
- Fix the issues in your theme code, starting with the six most common failures: low-contrast text, missing alt text, missing form labels, empty links, empty buttons, and a missing page language.
- Remove the overlay script and confirm nothing regressed.
- Publish an accessibility statement describing your WCAG 2.2 AA target and how to report problems.
Fudge can do the surfacing and the native-code fixes for you, then keep monitoring, which is the same workflow without the manual development time. You can also handle related improvements like editing existing pages and adding structured data in the same place.
FAQ
No. Overlays are automated JavaScript added on top of your existing HTML, and automated tooling only addresses 30 to 40% of WCAG criteria. They cannot fix most issues or supply the human judgment compliance requires. The FTC fined accessiBe $1,000,000 in 2025 for claiming otherwise.
Yes. Roughly 1 in 4 of the US ADA web lawsuits filed in 2024 named sites that already had an accessibility widget installed. In Murphy v. Eyebobs, a blind plaintiff sued a store running an overlay and the case settled. Overlay vendors' own terms often concede the product does not by itself meet the law.
More than 1,000 accessibility professionals, including WCAG contributors and screen-reader engineers, signed the Overlay Fact Sheet stating overlays are unreliable, cannot achieve compliance, and raise privacy concerns. The National Federation of the Blind has also condemned them.
An overlay is a script that runs on top of broken HTML without changing it, and you pay for it every month. Fixing the code repairs the underlying Liquid, CSS, and JavaScript so the page itself is accessible. Only the second approach holds up legally and improves the experience for real users.
Yes. accessiBe (accessWidget), UserWay, AudioEye, and Accessibly are widget-based overlays that inject JavaScript to display an accessibility menu and attempt automated fixes. They share the same core limitation: they cannot remediate most WCAG issues at the source.
Audit your store with a free tool like axe DevTools or WAVE plus a manual keyboard and screen-reader pass, then fix the issues in your theme code. Fudge can surface the issues, fix them in native code, and monitor for regressions, which removes the problem instead of hiding it.
