Do Accessibility Overlay Widgets Work?

If you've searched for "Shopify ADA compliance," you've almost certainly seen an ad for an app that promises to make your store fully compliant with a single script install. Click the icon in the corner, adjust the display, done. It's an appealing pitch — no developer, no code review, no waiting.

It's also not what the disability community, accessibility researchers, or increasingly, the courts think it is. Here's what these tools actually do, why they don't reliably prevent lawsuits, and what we recommend instead.

What an accessibility overlay actually is

An overlay widget is a JavaScript snippet you add to your site — usually via a Shopify app — that injects a small accessibility menu, typically a floating icon in a corner. Click it and you get options like larger text, higher contrast, a "dyslexia-friendly" font, reduced motion, and sometimes an AI-driven promise to "automatically fix" underlying code issues in real time as the page loads.

Products in this category (accessiBe, UserWay, and similar tools are the best-known names) market themselves as a fast path to legal compliance. The pitch is specifically aimed at store owners worried about lawsuits, which is exactly why it's worth scrutinising closely before you buy it.

Why overlays don't fix the underlying problem

The core issue is technical, not just legal. Real accessibility barriers live in your site's code — missing labels on form fields, a modal that traps keyboard focus incorrectly, an image with no alt text, contrast that's too low to read. An overlay runs on top of that code at runtime. It can change font size and colour. It generally cannot reliably rewrite broken semantic structure, restore missing labels with real context, or fix a keyboard trap it didn't create and doesn't fully understand.

Screen reader users in particular report that overlays frequently make their experience worse, not better — the injected JavaScript can override the assistive technology's own controls, introduce new keyboard traps, or announce confusing, duplicated content. Several major disability advocacy organisations have publicly stated that overlay widgets are not an adequate substitute for genuine, code-level remediation, and some screen reader users specifically ask sites to disable overlays entirely.

What the lawsuit record shows

This is the part that should worry overlay customers most: installing one doesn't reliably stop the lawsuits it's marketed to prevent. Our own accessibility scanner page cites a figure that's worth repeating here — 983 sites with accessibility overlay widgets installed were sued over web accessibility in 2025 anyway. The widget didn't function as a legal shield in those cases.

This tracks with what accessibility practitioners have been saying for years: plaintiffs' attorneys and their expert witnesses know how overlays work, test around them, and in some cases specifically target sites that rely on one instead of doing the underlying fix — because a site advertising "ADA compliant" via an overlay while still having real, testable barriers is, if anything, an easier case to build than a site that made no claims at all.

We're not citing a specific count of lawsuits that named an overlay vendor as a defendant, because we haven't independently verified that claim — treat any number you see quoted elsewhere on this specific point with the same caution.

What actually reduces your legal and UX risk

The unglamorous answer: fix the code. Specifically:

• Semantic HTML and proper labelling in your theme — labels tied to form fields, meaningful alt text, a logical heading structure. This is Liquid and markup work, not a script.
• Real keyboard testing across your homepage, product pages, cart, and checkout, fixing focus traps and missing focus states as you find them.
• Contrast and colour fixes in your theme's design tokens, so every page inherits them instead of relying on a runtime toggle.
• Auditing your app stack — popups, review widgets, chat bubbles — since third-party scripts are consistently where accessibility breaks in an otherwise clean theme.

Start with our Shopify ADA compliance checklist for the specific items to work through, and run a free automated scan to see where your store currently stands before you spend a dollar on remediation.

If you already have an overlay installed

You don't necessarily need to rip it out today. Some of the display-adjustment features (larger text, reduced motion, higher contrast) are genuinely useful to some users when they work correctly, and removing a tool your customers have gotten used to isn't automatically an improvement. What we'd recommend instead:

1. Stop treating the overlay as your compliance strategy. It's a nice-to-have feature, not a legal shield.
2. Run a real audit of your underlying theme and app stack — the overlay's presence tells you nothing about whether your actual code has barriers.
3. Fix what the audit finds, at the code level, on your own timeline rather than in a panic after a demand letter arrives.
4. Decide whether to keep the overlay as a supplementary feature once the real work is done, or drop it if it's causing more conflicts than it's worth.

Frequently Asked Questions

Are all accessibility overlay companies making false claims?

Not necessarily — reputable vendors in this space have walked back some of the "instant full compliance" marketing over the years in response to criticism. But the core technical limitation stands regardless of the vendor: a runtime script can't reliably rewrite broken underlying code the way a developer fixing the theme directly can.

Should I remove my overlay widget right now?

Not urgently, and not without a plan. Removing it doesn't fix anything on its own. Prioritise auditing your actual theme and app accessibility first; decide on the overlay afterward.

What's the difference between an overlay and genuine remediation?

An overlay adjusts the page at runtime, in the browser, after your code has already loaded. Remediation changes the code itself — your theme's Liquid templates, CSS, and JavaScript — so the fix is present every time the page loads, for every user, with or without the overlay's script running.

How do I know if my Shopify theme has real accessibility issues?

Run an automated scan for a baseline, then manually test keyboard navigation and a screen reader on your key pages — homepage, product page, cart, checkout. See our full checklist for the specific things to check.

Is it ever reasonable to use an overlay at all?

As a supplementary feature on top of a genuinely accessible theme, sure — some users like being able to adjust text size or motion themselves. As a replacement for fixing your code, no. The distinction is whether it's your only accessibility work or an addition to real remediation.