Why Accessibility Overlays Do Not Protect Against ADA Lawsuits

Accessibility overlays do not protect against ADA lawsuits. Overlays are JavaScript widgets that adjust font size, color contrast, and cursor behavior in the browser at runtime. They do not modify the underlying HTML, ARIA, or semantic structure of a page. UsableNet's annual ADA Title III digital-accessibility reports track filings against sites with overlays installed; overlay presence has not correlated with reduced litigation exposure. The 9th Circuit ruling in Robles v. Domino's Pizza, 913 F.3d 898 (9th Cir. 2019), established that websites tied to physical places of public accommodation are subject to the ADA regardless of remediation tools deployed, and overlays do not change that analysis.

What an accessibility overlay actually does

When you paste an overlay's script tag into your theme.liquid, the widget loads a button. A user clicks the button, a panel opens, and the user can toggle settings like "high contrast," "larger text," "pause animations." Behind the scenes, the overlay injects CSS overrides into the DOM and sometimes adds ARIA attributes via JavaScript.

What the overlay does not do:

1. Change the underlying source HTML
2. Restructure semantic markup (a <div> that should be <h2> stays a <div>)
3. Fix native form labels (only adds JavaScript-injected ARIA in some cases)
4. Resolve color contrast in the original CSS
5. Add real alt text to images that have no alt attribute (most overlays use AI to guess, often incorrectly)
6. Survive a page reload before the script executes (the page is briefly inaccessible)

The overlay solves the symptom of a non-accessible page only when the script has loaded, the widget is found, and the user knows to use it. None of those conditions are met in a typical screen reader user's workflow.

Robles v. Domino's: the controlling precedent

Guillermo Robles, a blind plaintiff, sued Domino's Pizza in 2016 because the company's website and mobile app were not navigable with the JAWS screen reader. He could not order a customized pizza online. The district court initially dismissed on due process grounds. The 9th Circuit Court of Appeals reversed in Robles v. Domino's Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), Case No. 17-55504.

The ruling established three points that matter for every Shopify merchant in the United States:

1. The ADA applies to websites and mobile apps that connect to a physical place of public accommodation.
2. The lack of specific DOJ regulations on web accessibility does not exempt operators from compliance.
3. Plaintiffs do not need to identify a specific federal regulation to bring a claim. The general ADA statute is sufficient.

The Supreme Court denied Domino's petition for certiorari in October 2019, leaving the 9th Circuit ruling as the operative law in the western United States. Subsequent rulings in the 11th Circuit (Gil v. Winn-Dixie, 2021), 2nd Circuit (Calcano v. Swarovski, 2022), and others have produced varied analyses, but the trend favors plaintiffs in nexus cases (sites tied to physical stores) and remains contested in pure-online cases.

The 9th Circuit framed the question as one of access, not effort: a website that excludes screen reader users is non-compliant regardless of which remediation vendors the operator engaged. The same analysis applies to overlay deployment.

The FTC accessiBe settlement

In January 2025 the United States Federal Trade Commission announced a settlement with accessiBe, the largest accessibility overlay vendor, over claims its accessWidget product made sites "ADA compliant". The settlement required a $1 million payment and prohibited accessiBe from continuing to claim that its product alone makes a website compliant with the ADA or WCAG. The FTC's action is the most authoritative federal record so far that overlay marketing has overstated what the technology delivers, and it is the clearest signal to merchants that an overlay does not equate to compliance.

A community-maintained statement against overlays, signed by hundreds of accessibility researchers and practitioners, is published at overlayfactsheet.com. It is the single best public reference for the technical reasons overlays fail to deliver real remediation.

The empirical pattern on overlay lawsuits

UsableNet has tracked ADA Title III digital-accessibility lawsuits annually since 2018, and their year-end reports are the most-cited public dataset on filing trends. Two findings recur across years: total ADA digital filings have grown each year, and overlay presence on a site does not lower the chance of being named in a complaint. Some plaintiffs' counsel now actively search for overlay-installed sites because the implementation pattern is trivially detectable: a script tag with a known vendor domain appears in the rendered HTML.

What overlays change in the page versus what real remediation changes

Here is a side-by-side. The left column is what an overlay does at runtime when the user clicks the widget. The right column is what a real fix in the theme code does.

Issue	Overlay behavior	Real fix in theme code
Missing form label	Injects aria-label via JS after page load	Adds <label for="email">Email</label> in customer-form.liquid
Image with no alt	AI generates guess at runtime	Author writes alt in product image field or alt="" for decorative
Insufficient contrast	Overlays a "high contrast" CSS layer	Updates the brand color token in base.css to meet 4.5:1
Heading hierarchy wrong	Cannot restructure (DOM order is fixed)	Refactors section.liquid to use proper H tags
Focus not visible	Adds focus ring via JS (not consistent)	Removes outline: none from global CSS
Skip-to-content missing	Sometimes injects a JS link	Adds <a href="#main">Skip to content</a> in theme.liquid
Pop-up traps focus	Cannot intercept third-party app DOM	Modifies app embed or removes the offending app

The real-fix column produces HTML that is accessible from the first millisecond of page load, survives reloads, works without JavaScript, and is auditable in the source code. The overlay column produces accessibility that depends on script execution timing and is invisible to most automated scanners and to screen reader users who turn off custom widgets.

Why this matters for Shopify merchants specifically

Shopify merchants face a particular risk pattern. Shopify themes use Liquid (a server-side templating language) and ship the rendered HTML to the browser. The HTML is what plaintiffs' attorneys, automated scanners, and screen reader users see. An overlay does not change the HTML. A theme edit does.

This is the design choice behind AccessifyAI. Every fix we generate is a real change to a Liquid file. You see the diff before you apply it. The change ships in your theme code, survives a page reload, and is reviewable in git. We do not inject a script. We do not promise compliance. We give merchants the same kind of code-level fixes that an in-house front-end engineer would write, applied through an app store install. See it on the Shopify App Store.

For more on what specifically fails in Shopify themes, see our breakdown of the 5 most-installed themes.

Frequently asked questions

Does any overlay vendor guarantee ADA compliance?

No reputable overlay vendor currently promises ADA compliance in their terms of service. Marketing language varies, but the contracts disclaim warranty of compliance. The FTC's 2025 settlement with accessiBe specifically required marketing language changes on this point.

What about overlays that use AI to fix code?

Overlays that claim AI remediation still inject changes at runtime via JavaScript. The underlying HTML the server delivers does not change. Some overlay vendors have begun offering "code export" features. If the export is real Liquid code you commit to your theme, you have left the overlay category and entered the remediation category. If it is still a runtime script, it remains an overlay.

Is using an overlay better than doing nothing?

Some users with low vision or motor impairments do benefit from font size and cursor adjustments. The overlay is not zero-value to those users. It is also not a defense against an ADA claim and it does not benefit blind users who rely on screen readers, which is the user group most often involved in litigation.

How do I know if my Shopify store has an overlay?

Open your storefront, view source, and search for known overlay vendor domains: userway.org, accessibe.com, equalweb.com, audioeye.com, accessible.org. If you find a script tag pointing to one of those, you have an overlay installed.

Can I be sued in 2026 in the United States?

Yes, if you operate a website accessible to US consumers. The ADA Title III digital-accessibility lawsuit count has grown year over year since 2017 per UsableNet's annual filings reports, which remain the most-cited public dataset on the trend.

Should I remove an overlay if I already have one?

Removing an overlay does not automatically improve accessibility. Removing an overlay and replacing it with real code remediation does. If you keep the overlay during a transition period, treat it as a stopgap, not a solution.