Migrating from UserWay to accessiBe

A step-by-step guide to switching platforms — what to save before you leave, how to disconnect, how to install accessiBe, and how to verify it’s working.

1. Before you switch — what to save from UserWay

Before cancelling or disconnecting your UserWay account, save the following. Some of these records may be needed for legal, procurement, or compliance purposes after you switch.

  • Your UserWay accessibility statement and compliance report — download from the UserWay dashboard
  • A list of domains and subdomains currently covered under your UserWay subscription
  • Any custom configurations or profile settings you have applied
  • Audit or scan report history for your records

Before canceling, contact UserWay support to confirm how long your data will be retained after account cancellation and request copies of anything you may need.

2. Remove the UserWay script from your site

Log in to your CMS or access your site’s theme files and locate the UserWay script tag. It is typically added to the <head> section of your HTML, or via a CMS plugin or tag manager.

WHAT TO LOOK FOR
A script tag referencing audioeye or audioeye in your page source. If you installed via a CMS plugin, deactivate and delete the plugin first. If via Google Tag Manager, remove the tag from your GTM container.

Important: Do not remove the UserWay script until you are ready to install accessiBe in the same session. There will be a brief window where no accessibility layer is active between removal and installation.

3. Install accessWidget

accessWidget is installed by adding a single script to your site’s <head> section, or via your CMS’s native accessiBe app or plugin.

Option A — Direct script install
Log in to your accessiBe dashboard, copy the installation script for your domain, and paste it into your site’s <head>. Full instructions: support.accessibe.com

Option B — CMS app (WordPress, Shopify, Wix, Webflow, Squarespace)
Install the accessiBe app or plugin from your CMS’s marketplace. Available on WordPress, Shopify, Wix, Webflow, and Squarespace. View all integrations →

4. Verify accessWidget is working

After installation, visit your website and confirm the accessiBe interface appears. The default position is the bottom-right corner of the page — this can be customized in your dashboard settings.

VERIFICATION CHECKLIST

  • accessiBe interface button appears on your site
  • Interface opens and accessibility profiles are accessible
  • Your domain appears in the accessiBe dashboard with an active status
  • Your accessibility statement has been generated (available in dashboard)

 

Initial scan and remediation runs within 48 hours of installation. The dashboard will update with your site’s accessibility status once the first scan is complete.

5. What’s included going forward

Once accessWidget is installed and verified, here is what your subscription includes:

  • Continuous scanning and remediation — site rescanned every 24 hours; accessibility adjustments applied on a session basis
  • Accessibility statement — generated automatically, hosted at a unique URL for your domain
  • Monthly audit reports — available in your dashboard
  • Litigation Support Package — included in Growth, Scale, and Enterprise plans
  • Expert services — manual audits, VPAT documentation, and MTCR available via accessServices

Getting support

If anything in the migration needs help, contact the accessiBe support team:

Contact accessiBe support →

Did you know?
accessiBe can help you solve at the source-code level. accessFlow gives your developers direct visibility into accessibility issues at the code level — continuous audits, prioritized issues, and clear remediation guidance built into the tools your team already uses, like Jira, GitHub, and CI/CD pipelines. Instead of managing accessibility only at the interface, your team can resolve the underlying issues where they start.

accessWidget and accessFlow work together:
accessWidget and accessFlow are part of the same accessibility ecosystem. accessWidget addresses accessibility issues for your visitors as they browse, while accessFlow helps your developers find and fix the underlying issues at the source. Together, they support accessibility efforts at both the interface and code levels.

More interesting content for you

Related articles

Ready to close your accessibility gaps?