Remove an Accessibility Overlay From WordPress

Removing an accessibility overlay from WordPress is a small job, but it has a trap: an overlay can reach a site in two ways, and removing only one leaves the other running. It may be a plugin, installed from the plugin list. It may be a snippet pasted into the theme, a header setting, or a tag manager. Find both before you declare the job done, test the site after removal, and then fix the underlying code problems the overlay was covering. Removal alone does not fix barriers. It only stops a script from adjusting the page at run time.

Step one: back up, and note what is installed

Before changing anything, take a backup of the site, or confirm a recent backup exists and can be restored. Note the overlay's name, where it appears on the site (usually a floating button or panel), and any contract or subscription tied to it, including its renewal date. Check the contract terms before cancelling a paid plan, because some plans renew automatically and some charge for the remainder of a term. This article covers the technical removal. Contract terms are yours to read, and a lawyer can advise if a term is unclear.

Step two: remove the plugin, if it is a plugin

Open the WordPress admin, go to Plugins, and find the overlay plugin by name. Deactivate it first, then check the live site: the floating button or panel should be gone, and the site's own menus, forms, and checkout or booking path should still work. If the site looks right with the plugin deactivated, delete the plugin. Deactivation alone leaves files and settings behind, and a future admin may reactivate it by accident. Deletion removes the plugin files. Check whether the plugin added its own settings page or menu item, and confirm those are gone after deletion.

Step three: remove the snippet, if it is pasted code

If no plugin matches, the overlay is likely a snippet: a short script tag pasted into the theme header, a theme settings field for header or footer code, a widget, or a tag manager container. Search the theme settings for header and footer code fields first, because that is where most snippets live on WordPress sites. Then check the theme's header template if you have file access, and any tag manager account tied to the site. Remove the snippet, save, and clear any caching plugin and server cache, because a cached page can keep showing the overlay for hours after removal. Check the live site in a private browser window, where no old cache hides the change.

Step four: test the site after removal

Removal changes what visitors see, so test the pages the overlay touched. Move through the homepage, a service or product page, and the contact form with a keyboard only, and confirm focus is visible and never disappears. Check that forms have labels, that links have names, and that the page language and skip link are present. A scan helps here: Axeazy's free scan runs in 60 seconds with no signup and no card, and the scan on the homepage covers the page you enter. Run it, save the dated report, and treat the result as the starting point for code fixes, not as a verdict on the site. The United States Department of Justice guidance says automated checkers can help, but a clean report does not mean everything is accessible, and a manual check paired with automated checks gives a better picture.

Step five: replace the overlay with code fixes

An overlay adjusted the page at run time. The source code underneath is unchanged, so the barriers it adjusted are still there. Work through them in code, in this order: labels on forms, names on buttons and links, heading order, keyboard order, and alt text on images. For WordPress sites, Axeazy's free plugin applies three render-time fixes at once: a skip navigation link, a page language attribute, and an alt text fallback, with no account needed, from Axeazy's WordPress plugin page. Paid plans add weekly scans and further fixes, and the scan runs 98 automated checks against WCAG 2.2 AA, grouped into 14 categories. Colour contrast is detected and a correct colour is calculated, but a visible colour change is never applied without owner approval, so plan an approval step for any colour change the scan finds.

If the overlay was added after a demand letter, pass the removal and the new scan to a qualified attorney before replying to anyone about the site. Removal plus a dated scan and a fix list gives an attorney facts. Removal alone gives an attorney a gap.

Related reading

For the migration roadmap beyond removal, read switching from an overlay to code level fixes, and for the comparison behind that choice, read overlay vs code fixes: which should you buy. For the WordPress tool list, read best accessibility tools for WordPress sites.

• For the Shopify version, read remove an accessibility widget from Shopify.

FAQ

Will removing the overlay break my site?

It should not, if the overlay only added a panel and run-time adjustments. Test menus, forms, and checkout or booking paths after removal, and restore from backup if anything breaks, then check whether the break came from the overlay or from another change made the same day.

Should I cancel the subscription at the same time?

Read the contract terms first. Technical removal and subscription cancellation are separate steps, and cancelling in the wrong order can leave a renewal charge or a gap in support. Remove the code, test the site, then cancel by the contract's own process.

What if the overlay button is still there after removal?

Clear every cache: the caching plugin, the server cache, and the browser cache, then check in a private window. If the button remains, a second copy of the snippet is still live, usually in a tag manager or a second header field. Search again before concluding the removal failed.

Last checked: October 31, 2026 Sources: W3C WCAG 2.2; ADA.gov web guidance; Axeazy capabilities and WordPress plugin pages.

Run Axeazy's free scan after removal, save the dated report, and work the fix list in code from there.