If your accessibility widget is a third-party overlay — a script sold on the promise it makes your site 'compliant' — yes, you should remove it, and doing so is safe. Deleting the code line reverts your site to whatever accessibility it had before, which is the honest starting point for a real fix. The one thing to confirm first is which kind of tool you actually have: a genuine user-preference widget (text size, contrast controls) on top of already-accessible code is fine to keep, while a 'compliance' overlay is the one worth pulling. This post walks through how to remove an accessibility overlay cleanly and what to put in its place.
Should I remove my accessibility widget?
Start by identifying which product is on your site, because the two are marketed to look identical. Attack the compliance claim, not the preference button.
A preference widget hands control to the visitor: bigger text, a high-contrast theme, paused animations. Layered on top of code that is already built accessibly, it makes no legal claim and is worth keeping. ADA Fail's own site runs one. A compliance overlay is different — it is a script you paste in that claims to detect and fix your accessibility problems automatically, usually with marketing like 'ADA compliant in 48 hours' or 'AI fixes your site.' The tell is the promise. If the tool claims to make a broken site compliant, that is the one to remove. We break the two apart in detail in accessibility widget vs. overlay.
Why remove an accessibility overlay at all?
Because it does not do the job it is sold to do, and keeping it can actively hurt you on two fronts: real users and legal exposure.
It doesn't fix the site for real users
Automated tooling of any kind can detect only roughly a third of WCAG success criteria. The rest — whether alt text is meaningful, whether reading order makes sense, whether a form error is understandable to a screen-reader user — need human judgment an in-browser script cannot supply. When researchers analyzed the top million homepages, sites running an overlay averaged roughly as many detectable errors as sites without one. The script did not move the needle. Overlays also frequently interfere with the assistive technology a disabled visitor already runs, which is why the National Federation of the Blind formally opposes them, describing them as 'not only ineffective but harmful.' There is more on the mechanics in why overlay widgets fail.
It doesn't protect you from a lawsuit
The data points the other way. More than 5,000 website and app accessibility lawsuits were filed in 2025, up roughly 20% over the prior year, part of 8,667 ADA Title III filings overall. UsableNet's year-end reporting repeatedly finds that hundreds of the companies sued each year already had an accessibility widget or overlay installed when they were sued. A plaintiff's attorney can see the overlay in your page source — far from a shield, it can read as an admission that you knew there was a problem and reached for the cheapest patch. It was also the compliance claim itself that drew the FTC's $1 million settlement with accessiBe in early 2025, over allegations the vendor deceptively promised its widget could make any website WCAG-compliant.
How do I remove an accessibility overlay?
Removal is almost always a matter of deleting the snippet the vendor had you install. Work through these steps.
- Find the script. Overlays load from a single line of JavaScript, usually near the closing </body> or in the <head> of your template. View your page source and search for the vendor's name or domain. On WordPress it is often in a header/footer plugin, the theme's header.php, or a 'custom code' field; on Shopify it is typically in theme.liquid or an installed app; on Wix, Squarespace, and other builders it lives in a custom-code or third-party-app panel.
- Cancel the subscription. Most overlays are billed monthly. Removing the code does not stop the billing — cancel through the vendor account separately so you are not paying for a script that is no longer running.
- Delete the snippet and clear caches. Remove the line, save, and purge any CDN or page cache so the old version stops serving. If the overlay came in as a plugin or app, uninstall it fully rather than just disabling it.
- Verify it's gone. Reload the site in a private window and re-check the page source. Confirm the button no longer appears and the vendor's script no longer loads. Test on both a phone and a desktop, since some builders inject code per template.
That is the whole removal. Nothing about deleting the overlay makes your site less accessible than it truly was — it simply stops hiding the real state of the code behind a button.
What should I do instead of an overlay?
Replace the false fix with a real one. Risk reduction here is unglamorous but durable: assess the actual code, remediate the defects, and keep testing as the site changes.
Begin with an honest assessment against WCAG 2.2 AA, the level courts, the DOJ rule, and the EU all reference. Automated scanning is a useful first pass — it reliably catches the most common failures across the web, which are low-contrast text, missing image alt text, missing form labels, and empty links or buttons. But passing an automated scan is not the same as conforming to WCAG; a clean automated-scan grade covers only the roughly one-third machines can judge. Full conformance is a question only expert human testing — including screen-reader and keyboard testing — can speak to. A plain-English ADA website compliance checklist will walk you through the essentials, and a free accessibility audit will tell you exactly what your code does and doesn't do, with no script to install.
Do I need to keep any kind of accessibility button?
No button is required by any standard. A preference widget is optional and, added on top of accessible code, a thoughtful convenience — but it is never a substitute for building the site correctly. If you received a demand letter that pushed you toward an overlay in the first place, handle the legal side before reaching for any quick fix: our guide on what to do about an ADA website demand letter covers the first moves.
Ready to replace the overlay with something that actually works? Get a free accessibility audit from ADA Fail. We'll confirm whether the tool on your site is a harmless preference widget or a liability-generating overlay, show you what your code truly does for real users, and give you a clear, plain-English path to fixing the site — not just hiding the problem behind a button.
Frequently asked questions
Will removing the overlay make my site fail accessibility tests it was passing?
No. An overlay does not actually pass the parts of accessibility that matter to real users — independent research found sites running overlays averaged roughly as many detectable errors as sites without them. Removing it doesn't lower your true accessibility; it just stops masking the real state of your code. The honest baseline you're left with is exactly what you need in order to remediate properly.
The overlay vendor's contract mentions legal support. Should I keep it for that?
Weigh what that support is actually worth against the record. Companies with overlays installed are sued every year, and the overlay is visible in your page source to any plaintiff's attorney. A vendor promise of assistance is not the same as a defensible, conformant website, and the compliance claim itself is what drew regulator action against at least one major overlay maker. Real remediation of the underlying code is what reduces the odds of a suit in the first place.
I'm on Shopify or WordPress and can't find the overlay code. What now?
Check the platform's app or plugin list first, since many overlays install as an app rather than a raw snippet — uninstalling the app removes the script. If it was pasted as custom code, look in the theme header/footer settings or a code-injection field. When in doubt, a free audit will detect the overlay for you and pinpoint where it's loading from, so you can remove it and see your genuine code-level accessibility underneath.