📊 Data-Driven Comparison

Accessibility Overlay vs. Source Remediation, and What to Do Instead

An overlay widget is rented by the year; source remediation fixes the code once. This page is for choosing between them: what each changes, what each costs over time, how to compare named providers, and how to replace an overlay you already run. Whether overlays work at all is answered below, with the evidence.

Compliapoint works on WordPress (including WooCommerce) and Shopify sites.

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 than the 56.1 average across all home pages, while WordPress sat 5.8% below it. Both platforms fail in specific, predictable places. An overlay cannot reach most of them.

24.9%of the 2025 ADA website lawsuits EcomBack counted named a site already running a widget
$1MaccessiBe must pay the FTC under its 2025 order
1,000+people have signed the Overlay Fact Sheet, as of October 2026
$390–$3,990a year for published accessiBe, UserWay and EqualWeb plans, renewed indefinitely

What You Would Be Installing

An overlay is a script that changes your pages in each visitor’s browser rather than in your code; the full definition is on What Is an Accessibility Overlay? For what that means at the code level, see why overlays fail.

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

❌ Overlay / Widget Approach

  • JavaScript injected at page load — cannot fix underlying HTML structure
  • Its fixes are guesses about what your content means
  • Cannot fix PDF, document, or video accessibility
  • More than 1,000 people had signed the Overlay Fact Sheet against them by October 2026
  • accessiBe was ordered in 2025 to pay the FTC $1 million over its compliance claims
  • 983 ADA website lawsuits in EcomBack’s 2025 count, 24.9% of the total, named sites already running one
  • Leaves your code exactly as it was; a tester using the live page gets whatever the script guessed, right or wrong
  • Remove the subscription — all "fixes" vanish instantly
  • Produces no record of fixes, because nothing in your code was fixed
  • Published plans run $390 to $3,990 a year, for as long as you keep the widget

✅ Source-Level Remediation

  • Fixes made directly in HTML, CSS, and template source files
  • Works through the browser’s own accessibility layer, with no script in between
  • PDFs tagged for screen readers, videos captioned per WCAG 1.2
  • Meets WCAG in the code itself, which is what the standard is written against
  • Nothing to claim beyond what the dated test record shows was verified
  • Documented finding by finding, with the fix and the date beside each
  • Dated accessibility test record and VPAT for procurement and legal defense
  • Repairs written where updates leave them alone: a child theme on WordPress, a recorded diff on Shopify
  • Complete audit trail documenting every finding and remediation action
  • One-time project cost — no forced ongoing subscription

Accessibility Overlay Problems: The Evidence

Do accessibility overlays work? Not as a route to WCAG conformance, and the people and bodies closest to the question have said so on the record.

What the record shows

  • Federal Trade Commission, 2025. On January 3, 2025 the FTC announced that accessiBe would pay $1 million to settle allegations that it misrepresented the ability of its AI-powered tool to make any website compliant with WCAG. The Commission approved the final order in April 2025.
  • National Federation of the Blind, 2021. Resolution 2021-04 called on overlay providers to “stop making misleading, unproven, and unethical claims”. In January 2025 the NFB filed comments supporting the FTC’s order.
  • The Overlay Fact Sheet, 2021. It states that overlays “are not an effective means of ensuring accessibility.” By October 2026 more than 1,000 people had signed it, among them people working at Google, Microsoft, Shopify, eBay, Target, CVS Health and Dell Technologies.
  • IAAP, 2022, and the European Disability Forum, 2023. The International Association of Accessibility Professionals published an overlay position and recommendations in early 2022. In May 2023 it and the EDF issued a joint statement that overlays “do not make the website accessible or compliant with European accessibility legislation.”
  • Practitioners, 2021. In WebAIM’s January 2021 survey of 758 web accessibility practitioners, 67% rated overlays, plugins and widgets that automate accessibility changes as not at all or not very effective. Among respondents with disabilities, the figure was 72%.
  • Lawsuits, 2024. UsableNet counted 1,023 companies sued in 2024 while an accessibility widget was live on their site, in a year of more than 4,000 digital accessibility lawsuits.

How the record built up

  • August 2020: disability rights attorney Lainey Feingold publishes “Honor the ADA: Avoid Web Accessibility Quick-Fix Overlays”.
  • March 2021: the Overlay Fact Sheet launches.
  • July 2021: the NFB adopts Resolution 2021-04.
  • May 2023: the EDF and the IAAP publish their joint statement.
  • June 2023: WebAIM reports that UserWay’s overlay rewrote pages only for its WAVE checker, producing zero-error results visitors never saw. UserWay removes the code within the week.
  • July 2024: Bloomsybox sues UserWay in federal court in Delaware, alleging it was sued for accessibility violations about five months after subscribing.
  • January and April 2025: the FTC proposes, then approves, its final order against accessiBe.
  • 2025: Illinois’ Department of Innovation and Technology advises against overlays on State websites.

What that means on a WordPress site or a Shopify store

Every item above comes back to one mechanism: the script edits the page in the visitor’s browser after your theme has rendered it, so the failures stay in the WordPress theme or the Shopify theme where they were written. The next section sets out where those failures sit on each platform.

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 often an icon-only social link in the theme; a missing form label is often 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 button-style variant pickers as a fieldset with a legend, labels its selects and its quantity input, and puts visually-hidden text inside its quantity 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 in August

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 now than it did in July 2026, 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.

Fixes That Stay Put

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 assistive technologies such as JAWS, NVDA, VoiceOver, Dragon and 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. It is the record an attorney, a procurement reviewer or an enterprise buyer will ask to see.

Already Running an Overlay? How We Replace It

Most people reading this page already pay for a widget. Replacing it is a sequence, and the order matters more than the speed: the widget comes off last, once the code underneath it no longer needs it.

1. Audit with the widget switched on

We test your site as visitors see it today, overlay included, so the report records what the widget changes and what it leaves broken. That before picture is part of your record.

2. Fix the source underneath it

Repairs go into a staging copy of your WordPress site or a duplicate of your Shopify theme, while the widget keeps running on the live store. Nothing your customers see changes until you approve it.

3. Remove the widget, then check again

Once the fixes are live, the plugin, app or theme.liquid line comes out, caches are cleared, and the site is tested again without the widget there to mask anything.

4. Cancel the subscription last

Only when the retest is clean do you cancel the overlay, with a dated test record and a full report in hand that stay yours. The engagement is priced like any other, by screen count, from $4,750.

Doing it yourself? Our step-by-step overlay removal guide covers the same order for WordPress and Shopify.

Frequently Asked Questions

Should I use an overlay or source remediation?
If you need your site to meet WCAG and a record that shows it, source remediation. An overlay changes the page in each visitor’s browser and leaves your code as it was, so there is nothing to record and nothing that stays when the subscription ends. Why overlays fall short is set out, with its sources, in the evidence above.
How do I compare overlay providers?
Ask each one three things: what it changes in your code, what remains if you stop paying, and what record it gives you of what was fixed. Our pages on accessiBe, UserWay, AudioEye and EqualWeb, linked below, answer those three for each.
Why did the FTC order an overlay company to pay $1 million?
In January 2025 the FTC alleged that accessiBe misrepresented its product’s ability to make any website WCAG compliant, and that it formatted paid reviews to look independent. accessiBe agreed to pay $1 million, and the final order, approved in April 2025, bars it from making those claims without evidence to support them.
Can an overlay hurt my legal position?
It does not protect it. EcomBack counted 983 ADA website lawsuits in 2025, 24.9% of the total, against sites already running a widget, and a widget leaves the code an expert would examine exactly as it was. How much it matters in your own case is a question for your attorney.
Is source remediation more expensive than an overlay?
Over a few years, usually not. Published plans from accessiBe, UserWay and EqualWeb run $390 to $3,990 a year for as long as you keep the widget; over three years that is $1,170 to $11,970, and nothing in your code has changed. Source remediation is priced once: a Complete Package is $4,750, $9,995 or $19,995 by screen count, with monitoring optional afterwards.
Do accessibility overlays work?
Not as a route to WCAG conformance. An overlay changes the page in the visitor’s browser after it loads: its repairs are guesses about content it cannot understand, it has to re-patch the page every time something changes, and it cannot touch PDFs, captions or your source code. The FTC’s 2025 order against accessiBe, NFB Resolution 2021-04 and the IAAP’s overlay position all point the same way.
My developer recommended an overlay. Should I trust that advice?
Most web developers are not accessibility specialists. Overlays are marketed heavily to developers as an easy solution they can install in minutes. The appeal is understandable — the alternative is learning WCAG 2.2, auditing every page manually, and making detailed code changes. But the ease of installation does not correlate with effectiveness. Accessibility specialists — the people who do this full-time — have signed a document opposing overlays. The developer's recommendation is likely well-intentioned but not informed by the current professional consensus.
Can overlays fix any accessibility issues at all?
Overlays can make minor cosmetic adjustments: font size, cursor size, contrast overrides, link highlighting. These features duplicate functionality already available in every operating system's built-in accessibility settings — settings that users with disabilities have already configured for their needs. The more serious violations — broken form labels, missing alt text, keyboard traps, heading structure, reading order — cannot be reliably fixed by injecting JavaScript after page load.
What if I already have an overlay installed and I receive a demand letter?
Contact us immediately through our assessment form or contact page. We can evaluate your site's actual source-code compliance beneath the overlay and scope a remediation plan. The process is straightforward: we audit your source code, remediate the violations, deliver the dated records of what was tested and changed, and you remove the overlay script. Your site becomes natively accessible.
Are there any situations where an overlay makes sense?
As a temporary measure while source-code remediation is actively underway — and only as a temporary measure — an overlay can provide some marginal improvement. However, it should never be treated as a permanent solution, and it should never be represented as achieving compliance. The moment your source-code remediation is complete, the overlay should be removed. Compliapoint's standard delivery is 7–10 business days, which makes a long-term "temporary" overlay unnecessary.
How do plaintiffs' attorneys find out I'm using an overlay?
Overlay scripts are trivially detectable. Technology lookup services such as BuiltWith publish lists of sites running a given overlay, so assume anyone looking for yours can find it. The overlay's JavaScript file is visible in your page source code. The floating widget icon is visible on-screen. There is no way to hide the use of an overlay from someone who knows what to look for — and plaintiffs’ firms know what to look for.

Choose the Approach That Actually Works

Our assessment takes about five minutes. We respond with a fixed-price proposal for source-level remediation — no overlay, no subscription, no shortcuts.

Start Your Assessment

Back to the start: What is an accessibility overlay?

Compare Compliapoint

Compliapoint vs accessiBe · Compliapoint vs AudioEye · Compliapoint vs UserWay · Compliapoint vs EqualWeb · Compliapoint vs Deque · Compliapoint vs EcomBack · Compliapoint vs Accessible.org · Compliapoint vs Accessibility.Works · All 10 providers compared