Loading…
Overlay widgets promise instant, one-line-of-code compliance. Manual audits are slower and cost more upfront. Here's what actually holds up — in browsers, with screen readers, and in court.
| Criterion | Overlay Widget | Manual Audit + Remediation |
|---|---|---|
| How it works | JavaScript snippet injected into your page that attempts to modify the DOM after it loads | Certified auditors manually test with screen readers, then engineers fix issues in your actual source code |
| Fixes semantic HTML issues | Cannot — runs after render and can't repair missing label associations or broken ARIA relationships | Yes — fixed at the source, in your codebase |
| Screen reader compatibility | Frequently conflicts with JAWS and NVDA; AT users often report the overlay makes pages harder to use | Verified against JAWS, NVDA, and VoiceOver as part of the testing methodology |
| Setup time | Minutes | 2–4 weeks for a full audit; remediation timeline depends on scope |
| Upfront cost | Low — typically a monthly subscription | Higher upfront — fixed-price proposal scoped to your site |
| Legal defensibility | Multiple overlay vendors have been named as defendants in ADA lawsuits; courts have not accepted 'we installed a widget' as a good-faith compliance defense | Produces a documented conformance statement and audit trail — the standard courts and DOJ point to |
| Ongoing maintenance | New pages and components require the overlay to re-scan and re-guess; regressions are common | Automated testing added to your CI/CD pipeline catches regressions before release |
Our Take
Overlays are not a compliance strategy — they're a script that runs after the fact. Independent research documented by the Overlay Fact Sheet, signed by over 800 accessibility professionals, shows overlays introduce new WCAG failures and cannot fix the structural issues that cause the majority of real barriers. If you've already installed one, the money spent on the subscription is better redirected to an audit that tells you what's actually broken.
Overlay vendors do offer some genuinely useful features — like adjustable text sizing or contrast toggles — but these do not constitute WCAG compliance on their own, and the core claim of 'automatic ADA compliance' is not supported by independent testing. They cannot fix the majority of real barriers, which live in the underlying HTML and JavaScript, not the presentation layer an overlay can touch.
Keep it if you like the surface-level UI toggles, but don't rely on it for compliance. Get a manual WCAG 2.1 AA audit to find out what's actually broken underneath. Most clients redirect their overlay subscription budget toward a proper audit and remediation sprint once they see the gap.
Overlays are a mass-produced software product with no human review of your specific site. A manual audit involves certified specialists testing your actual pages with real assistive technology — that expertise and time is the entire value being delivered, and it's why it produces a defensible result an automated script cannot.
Automated scanners (axe, WAVE, Lighthouse) are a useful supplement — they catch roughly 30-40% of WCAG issues quickly and cheaply. But they cannot detect problems that require human judgment, like whether alt text is meaningful or whether a keyboard focus order makes logical sense. We use automated scanning alongside manual testing, not instead of it.
Tell us about your site and goals — we'll help you decide the right path forward, no pressure.
Book a Free Consultation