Accessibility Overlay Alternatives That Actually Work
If you are questioning your overlay subscription, you are in good company. This guide compares the proven alternatives — audits, code remediation, CI testing, and training — by cost, effort, and how much legal risk each one actually removes.
Reviewed by Khushwant Parihar, CPACC
Updated
Why Teams Are Moving Away From Overlays
Accessibility overlays are third-party JavaScript widgets that promise automated ADA and WCAG compliance. We cover how they work — and why they fall short technically — in depth in our accessibility overlays guide. This page focuses on the practical question that follows: what should you do instead? Three developments have pushed that question to the top of many teams' agendas.
Technical Limits Are Real
A runtime JavaScript widget cannot rewrite inaccessible source code into conformant code. It cannot author meaningful alt text, restructure heading hierarchies, fix reading order, or make a custom widget keyboard-operable. The barriers stay in the page for assistive technology users.
Overlay Sites Still Get Sued
UsableNet's digital accessibility lawsuit reports have consistently documented hundreds of lawsuits each year filed against websites that had an overlay or accessibility widget installed — roughly a quarter of all web accessibility suits in recent report years. The widget is not a legal shield.
Regulators Have Acted
In January 2025, the FTC announced a settlement requiring overlay vendor accessiBe to pay $1 million over claims that its accessWidget could make any website WCAG-compliant, which the agency alleged were deceptive. The order also covered undisclosed paid endorsements.
Add to that the long-standing criticism from the accessibility community itself — the Overlay Fact Sheet has been signed by hundreds of practitioners and disability advocates, and the National Federation of the Blind has publicly criticized overlay marketing — and the case for a different approach is straightforward. Not sure whether your site currently runs an overlay? Our free overlay detector identifies installed widgets and the vendor behind them.
The 5 Real Alternatives, Ranked by Effort and Impact
None of these are as cheap as pasting a script tag — and all of them, unlike an overlay, actually change what assistive technology users experience. They are listed roughly in the order most teams should adopt them.
- 1
Manual Remediation Guided by a Professional Audit
High impactMedium–high effortThe gold standard. A qualified auditor combines automated scanning with manual keyboard and screen reader testing, produces a prioritized findings report mapped to WCAG 2.2 success criteria, and your team (or a remediation partner) fixes the issues in source code. This is the only approach that directly removes the barriers a lawsuit would cite. See our accessibility audit services and remediation support.
- 2
Semantic HTML and Design-System Fixes
High impactMedium effortA large share of common WCAG failures — unlabeled form fields, div-based buttons, missing landmarks, broken heading order — trace back to a handful of shared components. Fixing your design system's buttons, inputs, modals, and navigation once propagates the fix to every page that uses them. This is the highest-leverage engineering work in accessibility: semantic HTML gives you keyboard support, accessible names, and screen reader behavior for free.
- 3
Automated Testing in CI with axe-core
Medium impactLow effortAdd axe-core (via jest-axe, Playwright, or Cypress integrations) or Pa11y to your continuous integration pipeline so accessibility regressions fail the build before they ship. Automated checks only catch a portion of WCAG issues, but they catch them on every commit for near-zero marginal cost — the opposite economics of an overlay, which charges annually while fixing nothing in your code. Read our automated vs manual testing guide for where automation genuinely helps.
- 4
Professional Audit Plus VPAT / ACR Documentation
Medium–high impactMedium effortIf you sell to enterprises, education, or government buyers, a Voluntary Product Accessibility Template (VPAT), completed as an Accessibility Conformance Report, documents your actual WCAG and Section 508 conformance. Unlike an overlay badge, an ACR is produced from real testing evidence, holds up in procurement reviews, and demonstrates the documented good-faith effort that matters in legal contexts.
- 5
Team Training
Compounding impactLow–medium effortTraining designers, developers, and content authors on WCAG 2.2 changes the cost curve permanently: teams that understand accessibility stop introducing new barriers, so every future feature ships accessible by default. A practical starting point is working through the WCAG 2.2 checklist against a real page your team owns.
Cost and Benefit: Overlay vs Remediation vs Audit + Remediation
Figures below are typical market ranges for small-to-mid-size sites; complex applications cost more. The decisive column is not price — it is whether the approach removes barriers from your code.
| Factor | Overlay widget | In-house remediation | Audit + remediation |
|---|---|---|---|
| Typical cost | ~$490–$5,000/year, forever | Engineering time (varies widely) | ~$3,000–$30,000+ one-time, then maintenance |
| Fixes source code | No | Yes | Yes |
| Issue coverage | Cosmetic adjustments only; automated detection misses most WCAG issues | Good for known patterns; risks blind spots without expert review | Full WCAG 2.2 coverage including manual-only issues |
| Lawsuit risk reduction | Minimal — overlay-equipped sites are sued regularly | Substantial, proportional to what you fix | Strongest — barriers removed and documented |
| Benefit to disabled users | Little; widgets can conflict with assistive tech users already have configured | Real and permanent | Real, permanent, verified |
| Long-term value | None retained if you cancel the subscription | Compounds — fixed components stay fixed | Compounds, plus VPAT/ACR evidence for procurement |
A Practical Migration Path Off an Overlay
You do not need to do everything at once. A realistic sequence for most teams looks like this:
- Week 1: Confirm what is installed with the overlay detector, check your contract's renewal date and cancellation terms, and run a baseline automated scan.
- Weeks 2–4: Commission a professional accessibility audit covering your key user journeys, tested with the overlay disabled so findings map to your real code.
- Months 1–3: Remediate in priority order — critical keyboard and form barriers first, then names/labels/alt text, then contrast and structure. Fix shared components before individual pages.
- Ongoing: Add axe-core checks to CI, remove the overlay script (check tag managers and CMS plugins), publish an accessibility statement, and schedule periodic re-audits.
Find Out What Your Overlay Is Hiding
Scan any URL with our free overlay detector to identify the installed widget and surface the WCAG violations that remain underneath it.
Frequently Asked Questions
Do accessibility overlays make you compliant?▾
No. Overlays inject JavaScript that adjusts presentation at runtime, but WCAG conformance depends on the underlying code: semantic structure, accessible names, keyboard operability, focus management, and meaningful alternative text. Automated tools — including the engines overlays rely on — can only detect a minority of WCAG issues, and no widget can rewrite broken markup into conformant markup. Courts and regulators have treated overlay-equipped sites as non-compliant when real barriers remain.
Are overlays ADA compliant?▾
The ADA does not certify products, so no tool can be 'ADA compliant' on its own. What matters is whether people with disabilities can actually use your site. Sites using overlays continue to be named in ADA lawsuits — UsableNet's litigation reports have repeatedly found hundreds of lawsuits per year filed against websites that had an accessibility widget installed. In January 2025, the FTC also ordered overlay vendor accessiBe to pay $1 million over claims that its product could make any website WCAG-compliant, finding those claims deceptive.
What is the lawsuit risk of keeping an overlay installed?▾
Installing an overlay does not reduce your exposure, and several accessibility attorneys argue it can increase it: the widget signals awareness of accessibility obligations while the underlying barriers remain detectable by the same automated scanners plaintiffs' firms use. Overlay vendor contracts also commonly disclaim liability for legal claims, so if you are sued, your organization bears the cost. The durable risk reduction comes from fixing the barriers in your code.
What should I do first after removing an overlay?▾
Run an automated scan and a keyboard-only pass to establish a baseline, then commission a professional audit that combines automated and manual testing. Prioritize fixes by user impact: keyboard access, form labels, accessible names, focus visibility, and alt text usually top the list. Our overlay detector tool can confirm the widget is fully removed, including copies loaded through tag managers.
Is remediation more expensive than an overlay subscription?▾
Upfront, yes — overlays cost roughly $490 to $5,000 per year, while a professional audit plus remediation for a mid-size site commonly runs from several thousand to tens of thousands of dollars. But remediation is a one-time investment in your actual codebase that compounds: fixed components stay fixed, your team learns the patterns, and your legal exposure genuinely drops. An overlay is a perpetual subscription that leaves every underlying barrier — and the associated lawsuit risk — in place.
Can I keep an overlay while I remediate?▾
You can, but be aware of the tradeoffs. Overlays can interfere with assistive technology, add page weight, and complicate testing because the widget mutates the DOM you are trying to fix. Many teams remove the overlay at the start of remediation so audits reflect the real user experience. If you keep it temporarily, make sure auditors test with the widget disabled so findings map to your source code.
Essential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences