Find my businessStart

How to cancel accessiBe and remove the script from your site

To cancel accessiBe, you do two separate jobs: stop the billing, then take the script off your website. Removing the script does not cancel the plan, and cancelling the plan does not take the script off. accessiBe's own help pages say so. This guide is for small business owners who bought a widget, now want out, and want to know what their site looks like the next day.

Leaving a widget and want to see what is really wrong on your site, with each fix written for your platform? Site Record tests up to 25 pages and rechecks monthly for 12 months: $499 once, no script added.

The short version: three steps in the right order

  1. Scan your site first. Run a free scanner on three pages and save the counts. You will compare them later.
  2. Cancel the plan. accessiBe says self-serve customers can cancel in its Customer Portal, and the license stays active until the end of the billing cycle you already paid for.
  3. Remove the script. Delete it from every page where it appears, save, and publish your site. Do this when the paid period ends, or sooner if you want it gone now.

Order matters because of what accessiBe's help pages say: uninstalling the widget does not cancel your subscription, and you keep getting charged until you cancel the plan on its own.

How do I cancel my accessiBe subscription?

From accessiBe's help center (read 2026-11-21):

The exact buttons in the portal change, so follow the current help article ("How to cancel an accessWidget license") on support.accessibe.com. We could not load that page in full when we checked, so we are not giving click-by-click steps we have not seen.

Tips that protect you

How do I remove the accessiBe script from my website?

The widget is a script, which means a line of code or a plugin that loads a file from accessiBe's servers on each page. accessiBe's uninstall article says to remove the script from every page it is on, then save and publish. Where it lives depends on how your site is made:

Your siteWhere to look
WordPressPlugins page: deactivate and delete the accessiBe plugin. If you pasted code, check the theme's header, a "header and footer" plugin, and any page builder's custom code box.
ShopifyApps page: delete the app. Then open the theme code and search for the script, since leftover lines can stay behind.
Wix, Squarespace, WebflowSettings, then custom code or "header code". Remove the line and publish.
Custom or hand-built siteSearch your files for "acsbapp". It is usually in the head or just before the closing body tag in a shared template.
A site your agency runsAsk them to remove it and send you a link to the page with it gone.

After you publish, open the site in a private window. The round accessibility button in the corner should be gone. If it is still there, the script is loaded from a second place. Common cases are a caching plugin that serves an old copy (clear its cache) or a copy in both the theme and a plugin.

What does my site look like after I cancel accessiBe?

Your site will look as it did before, plus anything you changed yourself. The toolbar goes. The patches the script made in the browser go too: labels or descriptions it added on the fly will not be there. This matters because those patches never changed your own files, so the same errors a scanner finds in your code are still there. For the longer explanation, read accessiBe alternatives.

Do not panic about this. The state your files were in all along is the real state of the site. Now you can see it and fix it.

What to do in the first week after you cancel accessiBe

  1. Rescan. Run the same three pages you scanned before. Compare the counts. The new numbers are the real ones. Our free checker guide shows how.
  2. Fix the top five. On small sites the same few errors cause most of the count: missing image descriptions, form fields with no labels, low contrast text, links that say only "click here" and buttons with no name. See the ADA compliant website checklist.
  3. Keep a keyboard test. Put the mouse away and Tab through your home page and contact form.
  4. Update your statement. If your site said "accessible, powered by accessiBe", change it to true words about what you tested. Use our accessibility statement template.
  5. Decide on help. Fixes cost roughly $1,500 to $3,500 once for a small site at agency rates (remediation cost), or less if you do them yourself.

What if you cannot find your accessiBe account?

This happens a lot, because the person who bought the plan is often not the person who runs the site now. Work down this list:

  1. Search your email for "accessiBe" and "accessWidget", including old addresses and the spam folder. The first email usually holds the login link and the receipts.
  2. Search your card statements for "accessiBe" or the company name on the charge. The date tells you the renewal date.
  3. Ask whoever built the site. An agency or freelancer may have bought it under their own account and passed the cost on to you.
  4. Check your platform. If you installed it from an app store, the charge may come through that store rather than from accessiBe.
  5. Write to accessiBe support from the email you used to buy, with your site address and the last four digits of the card. Keep the reply.

If a charge keeps coming after you cancelled, ask your card company how to dispute it, and send them your cancel proof. Do this quickly, because card companies set time limits.

Should I cancel accessiBe, or switch to something else?

That depends on why you bought it. If you bought a toolbar for visitors and like it, and your site is simple, keeping a widget is not wrong. If you bought it hoping to be safe from a lawsuit, know that in January 2025 the US Federal Trade Commission ordered accessiBe to pay $1 million over claims that its AI tool could make any website WCAG compliant, and over reviews that were not disclosed as paid. A subscription is not a legal shield. Sites with overlays have been named in suits; see the overlay lawsuit guide. We are not lawyers; if you got a letter, speak to one.

If you want to compare costs before deciding, see accessiBe pricing and what buyers say in reviews. If you are moving to another widget, accessiBe vs UserWay and AudioEye alternatives show that the others work the same way.

Common mistakes when you cancel accessiBe

Frequently asked questions

Does removing the accessiBe script cancel my subscription?

No. accessiBe's help center says uninstalling the widget does not cancel the plan. You must cancel the license separately or you will be charged again.

Can I get a refund when I cancel accessiBe?

The help article we found says the license stays active to the end of the billing cycle. It did not promise a refund. Check your terms and ask support in writing if you cancelled soon after a renewal.

How long until the widget disappears from my site?

The toolbar disappears when you remove the script and publish, plus any cache delay. If you only cancel the plan, expect it to stop working at the end of the paid period.

Will my site get sued if I remove accessiBe?

We cannot say; we are not lawyers. A widget was never a guarantee either way. What reduces risk is a site that people can use with a keyboard and a screen reader, plus a record of what you tested and fixed.

What is the cheapest way to replace accessiBe?

Free scanners and fixing the top errors yourself cost nothing but time. A written list of fixes is a middle option, and a developer is the most expensive but fastest.

Want the list of what is wrong on your site and how to fix it, paid once? Site Record, $499. More: all accessibility guides.

Sources