Accessibility widget for Drupal

Drupal already gives you a strong foundation for structured, standards-friendly markup, but the content editors and modules you rely on can still leave gaps for real visitors. ClearPath adds a front-end accessibility layer that people can open on any page to adjust the site to how they read and navigate.

You add it with a single script tag, and it works across every theme and content type without touching your render pipeline. Visitors get 25 tools, 14 languages, and 8 disability profiles, and you get an auto-generated accessibility statement plus analytics for your specific site.

How to add ClearPath to Drupal

  1. Install and enable the Asset Injector module, then go to Configuration, then Development, then Asset Injector, and choose JS Injector.
  2. Add a new JS injector, paste the ClearPath snippet into the code box, and set the condition so it loads on all pages of the site.
  3. Save and clear the Drupal cache under Configuration, then Performance, so the new asset is served right away.
  4. As an alternative, open your theme's html.html.twig template and paste the snippet just before the closing body tag, then rebuild the cache.

Where Drupal sites usually fail

  • Views-generated tables and exposed filters often render without proper header associations, so screen reader users hear column data with no row context when browsing a content listing.
  • Editors using CKEditor inside the body field routinely paste headings as bold paragraph text instead of real heading elements, which breaks the outline that assistive tech relies on to navigate an article.
  • Layout Builder blocks are easy to stack visually but the resulting DOM order can drift from the visual order, so keyboard and screen reader users move through a page in a sequence nobody actually designed.
  • Webform's multi-step forms frequently fail to announce validation errors on submit, leaving the focus sitting on the last field with no indication anything went wrong.

Why Drupal sites choose ClearPath

  • One script tag covers your whole Drupal site, so you do not have to edit templates for every content type or view.
  • The widget stays intact through core and module updates because it lives outside your theme logic.
  • The auto-generated accessibility statement is written in your site's language and reflects a live scan of your pages.
  • Per-site analytics show which tools your visitors actually turn on, so you can see the real demand on your content.

Questions

Should I use the Asset Injector module or edit the theme directly?

The Asset Injector module is the cleaner choice because the snippet survives theme changes and is managed from the admin UI. Editing html.html.twig works too, but you will need to re-add it if you switch or rebuild your theme.

Does ClearPath make my Drupal site fully compliant?

No. ClearPath helps you work toward WCAG 2.2, ADA, and EN 301 549 goals and gives visitors practical controls, but it does not replace fixing the underlying markup and content, and no widget can guarantee full compliance.

Does ClearPath make my Drupal site fully compliant?

No. ClearPath gives visitors real controls (text and contrast adjustment, reading aids, navigation help) and generates an accessibility statement from a live scan of your site, but it does not rewrite your theme's Twig templates, fix Views markup, or restructure a Layout Builder page. If the underlying HTML from your theme or modules has structural problems, ClearPath will not repair them. It is a genuine front-end layer for visitors, not a substitute for fixing markup at the source.