Accessibility Overlay vs. Source Remediation: Which Actually Works?
Overlay widgets promise instant ADA compliance for a monthly fee. The lawsuit data, the FTC, and 800+ accessibility professionals say otherwise. This page presents the evidence so you can make an informed decision about how to protect your business.
Almost every business facing this decision is on one of two platforms. WebAIM’s February 2026 scan of one million home pages found 252,302 running WordPress, averaging 52.8 detected errors each, and 42,516 running Shopify, averaging 75.1 — a third more errors than the web as a whole. Both platforms fail in specific, predictable places. An overlay cannot reach most of them.
What Is an Accessibility Overlay?
An accessibility overlay (also called a widget, plugin, or toolbar) is a piece of JavaScript that loads on your website and attempts to fix accessibility issues at render time. It typically adds a floating toolbar icon that lets visitors adjust contrast, text size, and spacing. Some products claim to use AI to automatically detect and repair WCAG violations.
Popular overlay products include accessiBe, UserWay, AudioEye, and EqualWeb. They typically charge $490–$3,990+ per year as recurring subscriptions.
The critical distinction: overlays modify how your page appears without changing your source code. When you remove the overlay script, your site reverts to its original inaccessible state. Nothing was actually fixed.
Where that script physically sits is the whole problem. On WordPress it arrives as a plugin that hooks into wp_head or wp_footer and injects the widget into every page the theme renders. On Shopify it arrives as an app embed block or a line in theme.liquid. Either way it loads after your theme, page builder, plugins and apps have already written the page — so it is reading the same broken markup a screen reader reads, and trying to correct it from the outside, on every single page load, forever.
The Head-to-Head Comparison
✅ Source-Level Remediation
- Fixes made directly in HTML, CSS, and template source files
- Works with every screen reader and assistive technology natively
- PDFs tagged for screen readers, videos captioned per WCAG 1.2
- Recommended by DOJ, W3C, and accessibility professionals universally
- No FTC actions — because no deceptive claims are needed
- Documented compliance that holds up in federal court
- Dated accessibility test record and VPAT for procurement and legal defense
- Permanent repairs that survive CMS updates, theme changes, and plugin updates
- Complete audit trail documenting every finding and remediation action
- One-time project cost — no forced ongoing subscription
The Evidence Against Overlays
FTC Enforcement (2025)
The Federal Trade Commission reached a $1 million settlement with accessiBe — the largest overlay provider — for making deceptive claims that its widget could make websites ADA compliant and conformant with WCAG standards.
Lawsuit Data (2025)
In the first half of 2025, 456 ADA website lawsuits (22.6% of all filings) targeted sites that had accessibility widgets installed. Monthly filings against widget-equipped sites exceeded 150 in a single month.
Overlay Fact Sheet
Over 800 accessibility professionals, disability advocates, and organizations have signed a public statement documenting overlay limitations and the harm they cause to users of assistive technologies. The statement is available at overlayfactsheet.com.
Technical Limitations
Automated tools — including AI-powered overlays — detect only 30–40% of WCAG violations. Keyboard traps, logical reading order, heading hierarchy, form labeling, ARIA patterns, and cognitive accessibility all require human evaluation and manual code repair.
Screen Reader Conflicts
Disability advocates report that overlays frequently interfere with screen readers (JAWS, NVDA, VoiceOver) by altering the DOM in ways that conflict with how assistive technologies parse page structure. Some users block overlays entirely.
No Document or Video Fixes
Overlays cannot fix PDF accessibility, add video captions, or remediate downloadable documents. These are among the most frequently cited violations in ADA demand letters and lawsuits.
Where WordPress and Shopify Actually Fail — and What an Overlay Does With It
Six failure types account for 96% of everything WebAIM detected across a million home pages: low contrast text (83.9% of pages), missing image alternatives (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%) and missing document language (13.5%). On WordPress and Shopify these are not randomly distributed. Each one has a known origin in the stack, and the origin is what decides whether a fix holds.
WordPress: four layers, one page
Your theme writes the header and navigation. A page builder writes the sections. Plugins write the forms, sliders, popups and cookie notices. Content writes the images and headings. An empty link is usually an icon-only social link in the theme; a missing form label is almost always the contact or checkout plugin, which the theme has no power to override. An overlay patches the rendered output of all four layers and re-patches it on every load. Update one plugin and the markup it was patching changes underneath it. We fix each layer where it is written — see how we remediate WordPress.
Shopify: 75.1 errors, and where they come from
Shopify stores averaged 75.1 detected errors — a third above the web average and 42% more than the average WordPress site. That is not the platform’s baseline. Dawn, Shopify’s own reference theme, builds its variant picker as a fieldset with a legend, labels its selects, gives its quantity input an aria-label and puts visually-hidden text inside its increment buttons. The errors arrive on top of that: third-party and heavily customized themes, app embed blocks that inject their own markup, custom sections added over years, product images uploaded with no alt text, and brand colors set in theme settings that fail contrast — low contrast alone appears on 83.9% of all home pages measured. Every one of those lives in Liquid, in theme settings or in your product data, which is where we fix them. Not one of them is fixed by a widget that only sees the page after it has rendered. See how we remediate Shopify.
The ARIA trap both platforms share
WebAIM found ARIA on 82.7% of home pages, averaging over 133 attributes each — a 27% increase in a single year. Pages with ARIA present averaged 59.1 errors against 42 for pages without it, roughly 17 additional barriers. WebAIM is careful to note this does not prove ARIA caused them, since pages using ARIA were also more complex. But it is the clearest signal available that adding attributes is not the same as fixing structure. Adding attributes at render time is precisely what an overlay does.
The Shopify door that closed last month
On August 26, 2026, Shopify sunset script tags on the Thank you and Order status pages for non-Plus stores, following the same sunset for Plus stores on August 28, 2025 and the removal of checkout.liquid from the information, shipping and payment steps. Any widget that reached those pages through a script tag stopped reaching them. If your subscription covers less of your store this month than it did in July, and nobody told you, that is a fair illustration of what a rented fix actually is.
Why Source Remediation Works
Source-level remediation addresses the root cause of every accessibility violation — the actual code that assistive technologies interact with. There's no JavaScript layer to fail, no subscription to expire, and no dependency on a third party's servers.
Permanent Fixes
Changes to heading structure, form labels, ARIA attributes, color contrast and keyboard navigation live in your source, not in a script layered over it. Where they live matters as much as what they say. On WordPress we work in a child theme or a site-specific plugin and never in parent theme files, because WordPress’s own handbook is blunt about the alternative: edit the parent theme and “the next time your theme is updated, your function will disappear.” On Shopify, where updating a theme replaces its files, we hand you the exact diff for every template we touch, so an upgrade is a re-apply you can see rather than a silent reversal.
Universal Compatibility
Native HTML fixes work with every assistive technology — JAWS, NVDA, VoiceOver, Dragon, Switch Access — without conflicts or render-time interference.
Coverage, and Its Honest Limit
Source remediation reaches everything your platform allows anyone to reach: templates, theme code, forms, PDFs, video captions and the interactive patterns automation cannot judge. One boundary is real, and we would rather state it than sell past it. Shopify’s checkout is Shopify’s code — its UI extensions run in a sandboxed Web Worker with no access to the checkout DOM, and extensions for the information, shipping and payment steps are Plus-only. No vendor can remediate that checkout. Not an overlay, and not us. We remediate your storefront to that boundary and record the checkout as a platform dependency in your VPAT, which is what a procurement reviewer and a plaintiff’s expert both expect to find.
Legal Defensibility
A dated accessibility test record, detailed audit report, and VPAT provide documented evidence of good-faith compliance. This is the strongest possible position for legal defense, settlement negotiation, or procurement qualification.
Frequently Asked Questions
Compare Specific Overlay Providers
Choose the Approach That Actually Works
Our assessment takes 3 minutes. We respond with a fixed-price proposal for source-level remediation — no overlay, no subscription, no shortcuts.
Start Your AssessmentRead more: Overlay Facts Hub