Why Overlay Widgets Don’t Fix Accessibility (And What Courts Say About Them)

If you’ve looked into web accessibility for your online store, you’ve probably seen ads for overlay widgets — JavaScript toolbars that promise instant ADA compliance with a single line of code. The pitch is appealing: paste a script tag, get a compliance badge, and never worry about accessibility again.

The reality is different. Overlays don’t fix the underlying accessibility problems in your website’s source code, and courts have made it clear they don’t count as compliance.

What Overlays Actually Do

Accessibility overlays are third-party JavaScript widgets that sit on top of your website. They typically add a toolbar icon that opens a panel with controls for font size, contrast, cursor size, and other visual adjustments. Some claim to use AI to automatically detect and fix accessibility issues in real time.

What they actually do is apply CSS modifications in the browser. They can increase font sizes, adjust contrast for the user who activates the widget, and add some visual enhancements. What they cannot do is fix the structural accessibility problems in your HTML:

• Missing alt text. An overlay cannot write accurate image descriptions for your product photos. It doesn’t know what’s in the image.
• Broken heading hierarchy. If your page jumps from H1 to H4, the overlay can’t restructure your HTML to fix the document outline.
• Inaccessible custom components. JavaScript-driven menus, modals, and carousels that lack proper ARIA attributes and keyboard handlers can’t be fixed by an external script that doesn’t understand your application logic.
• Form labeling issues. If a form field has no associated <label> element, the overlay cannot reliably determine what the field is for and generate an accurate label.
• Screen reader interference. Disability advocacy organizations, including the National Federation of the Blind, have documented cases where overlays actually made websites harder to use with screen readers by injecting conflicting ARIA attributes.

The FTC Settlement: $1 Million Fine

In January 2025, the Federal Trade Commission reached a settlement with accessiBe, one of the largest overlay vendors, over charges of deceptive marketing. The FTC alleged that accessiBe made false claims about its product’s ability to make websites compliant with WCAG standards and the ADA. The settlement included a $1 million penalty and a requirement to stop making unsubstantiated compliance claims.

The FTC’s complaint specifically noted that accessiBe’s product “did not make the websites on which it was installed fully accessible to people with disabilities” and that the company’s marketing claims were “false or unsubstantiated.”

800+ Businesses Sued Despite Using Overlays

According to research compiled by accessibility consultant Adrian Roselli and data from UsableNet’s annual reports, more than 800 businesses using overlay widgets have been named in ADA accessibility lawsuits. The presence of an overlay on a website has not successfully served as a defense in any of these cases.

In several cases, plaintiffs have specifically cited the overlay itself as evidence that the defendant was aware of accessibility issues but chose a superficial fix rather than addressing the underlying problems. Rather than providing legal protection, the overlay became evidence of knowledge of non-compliance.

Why Courts Reject the Overlay Defense

Courts evaluate ADA compliance based on whether people with disabilities can actually use the website — not whether a compliance tool is installed. When a screen reader user cannot navigate a checkout flow, it doesn’t matter that an overlay widget is present. The test is functional access, not the presence of a tool.

The DOJ’s position, expressed in multiple Statements of Interest filed in ADA web accessibility cases, is that WCAG 2.1 AA conformance is the relevant standard. Overlays do not produce WCAG conformance because they don’t fix the source code violations that WCAG measures.

What Actually Works: Source Code Fixes

The only reliable way to make a website accessible is to fix the actual HTML, CSS, and JavaScript. For Shopify stores, that means editing your Liquid theme templates to add proper alt text, fix heading structures, add form labels, ensure keyboard navigability, and include ARIA attributes where needed.

Source code fixes are permanent. They work for every user, on every visit, without requiring anyone to activate a widget. They address the root cause rather than attempting to paper over symptoms in the browser.

This is the approach AccessiShield takes. Rather than injecting a widget, AccessiShield scans your Shopify store for WCAG 2.1 AA violations, then generates specific Liquid template code patches that fix the issues in your theme’s source code. You review each fix, see exactly what changes, and apply the ones you approve.

It’s not instant and it’s not magic. But it’s how accessibility actually gets fixed.