Accessibility Overlays Don't Make You Compliant — They Just Make You Feel Like You Are

A client of ours had an accessibility overlay installed. They’d researched it, paid the subscription fee, and considered the compliance box checked.

Then they received a demand letter from an ADA plaintiff’s attorney.

The overlay was still running when the lawsuit arrived. It didn’t matter. The overlay had injected a layer of JavaScript over their site that announced itself as an accessibility solution — but it hadn’t touched the underlying HTML. The images still had missing alt text. The keyboard navigation still didn’t work. The form fields still had unlabeled inputs. The overlay had dressed the store up but hadn’t changed anything underneath.

This is the core problem with overlay widgets: they can’t fix structural HTML issues. They can remap some ARIA roles at runtime, adjust some color contrast, and resize some text. But they can’t add meaningful alt text to images they don’t understand. They can’t fix keyboard traps built into custom JavaScript components. They can’t make a checkout flow navigable with a screen reader if the underlying Liquid template wasn’t built that way.

And courts are increasingly aware of this.

What overlay vendors say vs. what courts have ruled

Overlay vendors market their products aggressively to ecommerce merchants as a compliance solution — low monthly fee, install once, done. Some make explicit claims about ADA or WCAG compliance.

The legal record doesn’t support those claims. Multiple federal courts have allowed ADA lawsuits to proceed against businesses that had overlay software installed, on the grounds that overlays don’t actually achieve WCAG 2.1 or 2.2 Level AA conformance. More specifically: plaintiff attorneys know how to test for real accessibility violations, and a JavaScript overlay doesn’t prevent them from finding them.

The argument that “we installed an accessibility tool” is not a legal defense. The argument that matters is “our site meets WCAG 2.2 Level AA.” Those are different things, and an overlay typically can’t get you to the second one.

What WCAG 2.2 Level AA actually requires

WCAG 2.2 Level AA is the standard most ADA lawsuits reference and the benchmark most legal guidance recommends. It’s not as complicated as the documentation makes it look. For an ecommerce site, the practical requirements are:

Keyboard navigation. Every interactive element — navigation menus, product filters, cart buttons, checkout steps, form fields, popups — must be fully usable with a keyboard alone. Tab order must be logical. Keyboard focus must be visible at all times.

Color contrast. Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). This catches a lot of light-gray-on-white design choices that look clean visually but fail for users with low vision.

Image alt text. Every image that conveys information must have descriptive alt text. Decorative images should have empty alt attributes so screen readers skip them. Product images, banner graphics, and icon buttons are all affected.

Touch targets. Clickable elements must be at least 24×24 pixels, with adequate spacing between adjacent targets. This is a WCAG 2.2 addition that specifically addresses mobile usability for users with motor impairments.

Form labels. Every form input must have a properly associated label. Placeholder text doesn’t count. This affects every email capture form, filter dropdown, and checkout input field on your site.

Focus indicators. When a user navigates by keyboard, the focused element must have a clearly visible indicator. Removing the default browser focus ring without providing a replacement is a WCAG failure.

None of these are things an overlay can fix after the fact. They require changes to your theme’s HTML, CSS, and JavaScript.

The 97% problem

Here’s the context that makes this feel less like a you-specific problem: according to the WebAIM Million — an annual accessibility analysis of the top one million websites — 97% of homepages have detectable WCAG failures. The average homepage has more than 50 distinct violations.

This means the vast majority of your competitors are equally exposed. And it means the plaintiff attorneys filing these cases are working from automated scan lists, not singling anyone out personally. They run a scanner, it returns hundreds of results, they send letters. The selection is largely random beyond “ecommerce store that has a contact form.”

The practical implication: the question is not “will I be targeted” but “when, and will I be prepared.”

What remediation actually looks like

The good news is that real WCAG 2.2 Level AA compliance for a typical Shopify store is a bounded project, not an ongoing subscription.

For most stores, a targeted accessibility remediation takes 10–20 hours of development work: auditing the existing theme against WCAG criteria, fixing keyboard navigation issues, adding proper alt text to images, labeling form fields, fixing contrast failures, and verifying the fixes with a screen reader test.

The cost of that work — roughly $1,500–$3,000 done properly — is less than the settlement amount on most ADA demand letters, and significantly less than litigation. It also doesn’t require a recurring subscription fee, doesn’t add JavaScript overhead to your store, and actually protects you legally in a way that an overlay doesn’t.

After the initial remediation, the maintenance requirement is light: ensuring new content and new features are built accessibly as they’re added. That’s a process change, not a continuous cost.

A basic self-audit before calling anyone

Before engaging a developer, you can run a quick first pass yourself:

1. Run your homepage through the WAVE tool (wave.webaim.org). It’s free, runs in your browser, and flags missing alt text, contrast errors, and structural issues with clear visual indicators.
2. Tab through your site with a keyboard. Press Tab from the top of your homepage. Can you reach every link and button? Is the focus indicator visible? Can you complete the checkout process without a mouse?
3. Check your contrast. Use a browser extension like Colour Contrast Analyser on your primary text and button colors. Anything below 4.5:1 is a failure.
4. Check your product image alt text. Right-click a product image, inspect element, and look for the alt attribute. Empty (alt="") is correct for decorative images. Missing entirely (alt attribute not present) is a WCAG failure.
5. Submit your contact form. Try filling it in with only a keyboard. Can you select every field, understand what each one is asking, and submit successfully?

These five steps will surface the most common issues. A formal audit will go deeper — heading structure, ARIA usage, dynamic content like modals and dropdowns, mobile touch targets — but this gets you a fast read on where you stand.

The overlay is not the answer

We’re not against accessibility tools. There are legitimate browser extensions and assistive technologies that genuinely help users with disabilities. The problem is specifically with accessibility overlay widgets marketed as a compliance solution for business owners — because they create the impression of compliance without achieving it, and they’ve been tested in court and lost.

If you’ve been running an overlay and assuming it’s handling your compliance, it’s worth taking an honest look at whether your site actually meets WCAG 2.2 Level AA. The easiest way to find out is to run a real audit. The cost of finding out is much lower than the cost of finding out the other way.

We do ecommerce accessibility audits as part of our broader site audit service, and we’ve helped several clients through the remediation process. It’s not a complicated project when you approach it systematically — it just has to actually be done, not simulated.

Last Updated: March 2026