Frequently Asked Questions
What does this widget actually do?
It gives your visitors a floating panel with controls for font sizing, contrast modes, a dyslexia-friendly font, text-to-speech, animation pausing, and more. Think of it as surfacing the kind of accessibility preferences browsers already support, just in a way that's easier to find and use.
Does this widget make my site WCAG compliant?
No. No widget can do that. Real compliance requires semantic HTML, proper ARIA attributes, keyboard navigation, meaningful alt text, and ongoing testing — all baked into your code. This widget is a complement to that work, not a substitute for it.
We support the Overlay Factsheet and are upfront about what overlays can and can't do.
How is this different from other accessibility overlays?
Most commercial overlays promise automated compliance. We don't. This is a free, open-source tool that gives visitors useful preference controls — nothing more, nothing less. There's no AI remediation, no legal compliance claims, and no tracking. Just a lightweight panel your visitors can use if they want to.
Is it really free?
Yes. It's MIT-licensed open-source software. There's no free tier with upsells, no paid version, and no premium features behind a paywall. You can use it, fork it, modify it, and redistribute it.
Does the widget collect any data or use cookies?
No. The widget runs entirely in the visitor's browser. It doesn't phone home, set tracking cookies, or collect any personal information. User preferences are stored locally in the browser using localStorage.
Will it slow down my website?
It shouldn't. The widget is a single lightweight script that loads alongside your page. It only activates its features when a visitor interacts with it.
How do I install it?
Add one script tag to your HTML:
<script src="https://cdn.jsdelivr.net/gh/ifrederico/accessible-web-widget@latest/dist/accessible-web-widget.min.js"></script>
No configuration required. For more control, you can pin a specific version or self-host the file.
What platforms does it work with?
Anything that lets you add a script tag — WordPress, Shopify, Squarespace, Wix, static sites, custom-built apps, and so on. It runs on top of your existing page without modifying your underlying markup.
Can I customize the widget's position, size, or language?
Yes. You can set the position, offset, button size, language, and icon through simple HTML data attributes. Text-to-speech voice and speed are also configurable. See the Configuration section for details.
What languages are supported?
The widget interface is available in 10 languages. The language can be set via the
data-acc-lang attribute.
Does the widget modify my website's code or design?
No. All changes are applied client-side in the visitor's browser and only affect their session. Nothing is altered in your source code, and other visitors see your site exactly as you designed it.
Does the widget help me find actual accessibility issues in my code?
Yes. Add ?acc-dev=true to any page URL to activate dev mode, which runs an inline
accessibility audit powered by axe-core. It'll flag real issues in your markup — missing
alt text, poor contrast ratios, ARIA problems, and more.
This is meant for development, not production, but it's a good starting point for the work that actually matters.
I found a bug. Where do I report it?
Open an issue on GitHub. Please include your browser and version, steps to reproduce, expected vs. actual behavior, and screenshots if possible.
How can I contribute?
We welcome contributions. See CONTRIBUTING.md for setup instructions, testing info, and how to submit a pull request.
No matching questions found.