Do accessibility overlays comply with ADA Title II?
Overlays and widgets can help with a few on-page issues, but they generally don't make a site or its documents conformant on their own. Here's the honest picture.
What an overlay is
An accessibility overlay (also called a widget or plugin) is a piece of JavaScript added to a website that puts an accessibility menu on the page, often a small icon that opens controls for font size, contrast, and similar adjustments. Common examples are marketed under names like accessiBe, UserWay, and AudioEye. They are quick to install, which is part of the appeal.
The short answer
Why overlays fall short
The rule requires the underlying content to meet WCAG 2.1 AA (Source: 28 CFR ยง 35.200 ) . An overlay sits on top of that content at runtime and can adjust some presentation, but it generally can't fix the structural problems that block assistive technology, things like missing semantic markup, incorrect reading order, unlabeled form fields, and untagged tables.
A few patterns to be aware of:
- Litigation has continued. Sites running overlays have still been named in digital accessibility lawsuits, so an overlay generally isn't a reliable shield.
- Screen-reader users often disable them. Many people who rely on assistive technology turn overlays off, because the overlay can conflict with the tools they already use.
- Automated by nature. Overlays lean on automated detection, which usually catches only part of real accessibility barriers.
Overlays and documents
This is the part that tends to get missed. An overlay operates on the web page. It generally does nothing for the PDFs, Word files, and other documents linked from that page, and for most public entities the document library is the largest part of the backlog. So a site can have a widget in the corner and still have a document estate that doesn't meet the standard.
What to do instead
Treat conformance as work on the actual content, not a script on top of it:
- Bring web templates and components up to WCAG 2.1 AA so new pages start accessible.
- Remediate the document library by use and risk, and fix authoring workflows so new documents go out accessible. See the readiness checklist and documents guidance.
- Validate with assistive technology and keep a dated record of the work for your compliance file.
None of this means an overlay is harmful on its own. It means it isn't the finish line, and for documents it generally isn't even the starting line.