Skip to main content
Accessify

Fix it right in the Designer.

Audit your published site, add the visitor panel, and see exactly which classes fail.

No coding required · 14 day free trial on paid plans · Remove it anytime

An ecommerce catalogue with a new product, its alt-text description and a visitor accessibility panel. An article page with a selected heading connected to a concise H1, H2 and H3 content outline. Desktop and mobile page previews with keyboard focus highlighted on their action buttons. A designed webpage with its selected heading connected to a section, heading and button structure rail.

How to install on Webflow

Find your platform’s code in your account. Shopify and WordPress also have official listings.

Create your Accessify account · Sign in

Shopify App Store · Official WordPress plugin

  1. Create your free Accessify account
  2. Copy the unique installation script from your dashboard
  3. Add the script to your project's custom code before the closing body tag, then publish.The exact steps for this platform are in the product.

The snippet

Your account has a unique snippet. Sign in to copy it from your dashboard.

Loads asynchronously, outside the critical rendering path.

Then validate it

If the panel isn’t detected, use Validate installation.

One class change can fail contrast on every page.

New store issues arrive as tasks.

Global classes

One colour token edited in the Designer changes everywhere, including new contrast failures.

Interactions

Custom interactions are a common source of keyboard traps and focus that goes nowhere.

CMS collections

Collection items publish without alternative text; the inventory catches them as they appear.

Publishing

Every publish is a change worth rescanning, which is what monitoring is for.

Store speed is revenue. We protect it.

  • The script is async and off the critical rendering path
  • Scanning and remediation run in our infrastructure, not the visitor's browser
  • The panel renders only when a visitor opens it
  • If you can measure a regression, that is a bug we want to see: send us the trace

What no third-party script can fix here

  • Fixes belong in the Designer. A script can't restructure your build.
  • Custom interactions may need rebuilding to be keyboard-operable; the record tracks that as manual work.
  • Findings are reported against the published site, so unpublished staging changes are not scanned.

Webflow questions

Where do I put the script?

In your project's custom code, before the closing body tag. Then publish.

Will it fight my interactions?

The panel doesn't touch interactions. Focus traps are reported for you to rebuild.

Does it audit CMS pages?

Yes. New collection items appear in the next scan and the alt text inventory.

Can it fix contrast for me?

It lists every failing element and its ratio. Changing the class is your design call.

Installed on your platform

The installed app, before configuration.

Accessify installed and ready to configure, with a Start setup action and pending accessibility settings.

Account identifiers and customer URLs are redacted.

The same snippet, four ways in.

Installation differs by platform; the script works the same.

See what your Webflow site looks like today.

Audit a product page before installation.