Remove an Accessibility Widget From Shopify

Removing an accessibility widget from Shopify is a small job with the same trap as on any platform: a widget can reach a store in two ways, and removing only one leaves the other running. It may be an app, installed from the app list. It may be code pasted into the theme, usually in the theme layout file or a theme setting for extra scripts. Find both before you declare the job done, test the store after removal, and then fix the underlying code problems the widget was covering. Removal alone does not fix barriers. It only stops a script from adjusting the page at run time.

Step one: back up the theme, and note the subscription

Before changing anything, duplicate the live theme, so the current version with the widget is saved under a new name. Note the widget's name, where it appears on the store (usually a floating button or panel), and any app subscription tied to it, including its renewal date. Check the app's billing terms before cancelling, because some apps bill for the remainder of a cycle. This article covers the technical removal. Billing terms are yours to read, and a lawyer can advise if a term is unclear.

Step two: remove the app, if it is an app

Open the Shopify admin, go to Apps, and find the widget app by name. Delete it from the app list, and confirm the floating button or panel is gone from the live store. Some apps leave code behind in the theme after deletion, so do not stop here. Open the theme editor and check the theme layout file and any app embed blocks for leftover script tags or settings tied to the app's name. Remove leftovers, save, and check the live store again in a private browser window, where no old cache hides the change.

Step three: remove the code, if it is pasted into the theme

If no app matches, the widget is likely a snippet pasted into the theme: a script tag in the theme layout, a setting for extra scripts, or a section added to the theme. Work on a duplicate of the theme first, never on the live theme. Find the snippet by searching the theme files for the widget's name or its script address, remove it, save the duplicate, preview the duplicate, and only then publish the duplicate as the live theme. If the snippet sits in a third party tool such as a tag manager, remove it there as well, and confirm the store no longer loads the script by checking the live pages after publishing.

Step four: test the store after removal

Removal changes what shoppers see, so test the paths that matter for a store. Move through the homepage, a product page, the cart, and the checkout with a keyboard only, and confirm focus is visible and never disappears. Check that product options, quantity controls, and form fields have labels and names, and that error messages on the checkout are readable. 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. 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 widget with code fixes

A widget adjusted the page at run time. The theme code underneath is unchanged, so the barriers it adjusted are still there. For Shopify stores, Axeazy scans the site and gives a guided checklist with computed fix values that the merchant or their theme editor can follow, rather than changing templates automatically. Work the checklist in this order: labels on forms and product options, names on buttons and links, heading order on product and collection pages, keyboard order through cart and checkout, and alt text on product images. The scan behind the checklist 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, because colour on a store touches brand and product presentation. Check the plan figures for a store of your size on Axeazy's pricing page before you choose a plan for the checklist work.

If the widget was added after a demand letter, pass the removal and the new scan to a qualified attorney before replying to anyone about the store. 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 Shopify tool list, read best accessibility tools for Shopify stores.

FAQ

Will removing the widget break my store?

It should not, if the widget only added a panel and run-time adjustments. Test product pages, cart, and checkout after removal, and restore the duplicated theme if anything breaks, then check whether the break came from the widget or from another change made the same day.

Should I cancel the app subscription at the same time?

Read the billing terms first. Technical removal and subscription cancellation are separate steps, and cancelling in the wrong order can leave a charge for the rest of a cycle. Remove the code, test the store, then cancel by the app's own process.

What if the widget button is still there after removal?

A second copy of the code is still live, usually as an app embed block, a leftover theme snippet, or a tag manager script. Check all three, clear caches, and check in a private window before concluding the removal failed.

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

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