Accessibility widget for WordPress

One script tag adds a full accessibility control panel to any WordPress site — no plugin, no account, no monthly fee.

No plugin required

AccessPath is not a WordPress plugin — it is a framework-agnostic script that runs on any site, WordPress included. That means no plugin to keep updated, no PHP, no database writes, and nothing that can conflict with your other plugins. You add one <script> tag and every page gets a floating accessibility button.

Add the script

<script src="https://cdn.jsdelivr.net/npm/@accesspath/embed@0/dist/embed.js"
        data-theme="light"
        data-storage-key="accesspath-prefs"
        data-position="bottom-right">
</script>

Pick whichever of these fits your setup:

A code-snippet plugin (WPCode, Code Snippets, Header Footer Code Manager) — paste it as a site-wide header or footer snippet.
Your theme — add it to header.php before </head>, or use the theme’s "custom scripts" / "header code" field if it has one (most modern themes and Astra, GeneratePress, Kadence, Blocksy do).
A Custom HTML block in a reusable/synced pattern that appears on every page, if you cannot edit templates.
Your host — some managed hosts (e.g. WP Engine, Kinsta) have a site-wide script injection setting.

It works the same with the block editor, Elementor, Divi, Beaver Builder, Bricks, or a classic theme — the widget sits above the page, not inside it.

Customize it

Every option is a data-* attribute on the same script tag — brand color, trigger shape and position, which profiles and sections show, language, and more. Build your exact snippet visually in the Install & Customize section on the home page.

There's also a built-in Accessibility Checker (an on-page WCAG scan for developers). It's off by default so your visitors never see it — add data-sections="profiles,quick,controls,actions,audit" to turn it on, e.g. on a staging site while you fix issues.

Prefer to self-host the file?

Download embed.js, drop it in your theme or uploads folder, and point src at that path instead of the CDN. Nothing else changes. The widget never calls back to us either way.

An honest note on compliance

AccessPath does not make a WordPress site "ADA compliant" or "WCAG compliant," and neither does any other overlay or widget. It helps visitors adapt your pages — bigger text, more contrast, less motion, a dyslexia-friendly font, read-aloud — but the underlying work (alt text, headings, labels, keyboard support, contrast) is still yours to do. Be skeptical of any product that promises automatic compliance. The Accessibility Guide spells out exactly what the widget does and does not do.

Free, open source, no lock-in

MIT licensed. No account, no per-visitor pricing, no subscription tied to your traffic. Remove the one line and it is gone cleanly. Source on GitHub; full docs in the Integration Guide.

FAQ

Is there an AccessPath WordPress plugin?

Not yet — and you do not need one. AccessPath is a single small script tag that runs on any WordPress site regardless of theme or page builder. You can add it through your theme, a code-snippet plugin, or your host’s custom-HTML settings.

Where do I paste the script?

Anywhere that injects markup into every page: your theme’s header/footer template, a snippet plugin such as WPCode, or a site-wide custom-HTML / header-scripts field. It works in the or before .

Does it slow WordPress down?

No. The script loads asynchronously, makes no external network calls after it loads, and does not touch PHP, the database, or page-generation time.

Does it make my WordPress site ADA or WCAG compliant?

No. AccessPath lets visitors adjust presentation to their needs, but it does not fix missing alt text, poor heading structure, unlabeled forms, or keyboard traps. Treat it as one helpful layer on top of real accessibility work, not a substitute for it.

Does it collect visitor data?

No analytics, no cookies, no tracking. Each visitor’s preferences are saved only in their own browser’s localStorage.