Overlays and widgets promise fast accessibility. They add a layer on top of your pages. They do not fix your templates, components, content, or journeys.
What an overlay is
- An overlay is third party JavaScript injected into your site.
- It runs after the page renders.
- It usually adds a floating button with controls for text size, contrast, fonts, and similar toggles.
Why overlays fail
-
They miss context.
Automation cannot judge intent, meaning, or task flow. -
They add a second interface.
Many users already rely on their own assistive tech and browser settings. -
They create new failure points.
Extra UI and scripts increase the chance of broken focus, labelling, and reading order. -
They slow down real fixes.
Teams stop funding remediation once a badge is live.
The A11Y Project advises against permanent overlay plugins Source 1 . Scope explains why overlays and widgets do not improve accessibility Source 2 . EDF and IAAP warn about interference with assistive technology and user settings Source 4 . WebAIM’s practitioner survey reports low effectiveness ratings Source 3 .
What to do instead
- Audit key journeys against WCAG 2.2 AA.
- Fix issues at source in templates, components, and content.
- Retest with keyboard and screen readers.
- Publish an accessibility statement with a feedback route and response process.
Sources
- [1] The A11Y Project. Should I use an accessibility overlay?. Back to article
- [2] Scope. Why accessibility overlays and widgets do not improve your website accessibility. Back to article
- [3] WebAIM. Survey of Web Accessibility Practitioners, results, overlay effectiveness. Back to article
- [4] European Disability Forum and IAAP. Joint statement on accessibility overlays. Back to article