Ability Bazaar guide
Why an accessibility overlay does not make a website compliant
The short answer
An accessibility overlay is software added to a site—often through a JavaScript snippet or widget—to change presentation, offer preferences or attempt automated fixes. It may help in limited situations, but installing one does not by itself establish WCAG conformance or ADA compliance.
The U.S. Department of Justice says automated checkers and overlays can be helpful when used carefully, but a clean report does not necessarily mean a site is accessible. In 2025, the Federal Trade Commission finalized an order against an overlay vendor over unsupported claims that its product could make any website WCAG-compliant.
Important: This page discusses testing and remediation practice, not whether a particular product or website satisfies a law. Seek legal advice for that question.
What can an overlay legitimately do?
A page-level tool may provide display preferences, expose a feedback channel, flag machine-detectable problems or apply narrowly defined changes. Those functions can be useful when they are described accurately, tested with assistive technology and do not interfere with a user's own settings.
The problem is not the existence of automation. It is treating an automated layer as a substitute for fixing the product and verifying the result. Claims should match the tool's tested capabilities and should never promise universal compliance.
What barriers usually require changes to the underlying product?
- A workflow whose focus order does not follow the intended task.
- A custom control with the wrong keyboard behavior, name, role or state.
- Instructions and error recovery that are confusing or incomplete.
- An image whose correct text alternative depends on its purpose and context.
- Documents, video, authentication and third-party components outside the overlay's reach.
- A design or release process that keeps creating new barriers.
Does an overlay reduce legal risk?
No technology can promise that outcome in every jurisdiction and fact pattern. The FTC's final order is a useful warning: broad compliance and testing claims need reliable substantiation. A widget also does not change the DOJ's core message that online goods, services and programs must be accessible.
Public lawsuit totals from advocacy or vendor reports can use different definitions and may not represent every filing. This guide therefore does not publish a universal lawsuit count. Organizations should ask counsel about their circumstances and focus operationally on removing barriers.
What is a more durable improvement path?
- Publish an accessible feedback route and respond to reported barriers.
- Inventory critical pages, documents and workflows.
- Combine automated checks with manual standards-based evaluation.
- Test representative tasks with people who use assistive technology.
- Fix reusable components and source templates before isolated pages.
- Add accessibility acceptance criteria and regression tests to every release.
- Retest after remediation and record remaining limitations honestly.
Frequently asked questions
- Can an accessibility overlay be useful?
Sometimes. A narrowly described tool may provide preferences or help find issues, but it should be tested and must not be presented as a complete compliance solution.
- Does an overlay prove WCAG conformance?
No. WCAG conformance depends on the actual content and complete user experience, including requirements that need human judgement.
- What should replace an overlay-only strategy?
Use accessible design and code, automated and manual testing, involvement of disabled users, documented remediation and ongoing regression checks.
Sources
- ADA.gov, Guidance on Web Accessibility and the ADA
- Federal Trade Commission, Final Order on Unsupported Automated Accessibility Claims
- W3C WAI, Involving Users in Evaluating Web Accessibility
Sources were checked on August 21, 2026. Regulations, standards and product documentation can change; follow the linked source for the latest version.