Comparison
AllyProof vs. accessibility overlays
Accessibility overlays promise instant compliance from a single line of JavaScript. In practice they mask a slice of issues in the browser without fixing your code - and they’ve drawn thousands of lawsuits and, in 2025, an FTC action against overlay vendor accessiBe. AllyProof takes the opposite approach: find the real WCAG violations, fix the source, and prove the work.
| Capability | Overlay / widget | AllyProof |
|---|---|---|
| Fixes the underlying code | ||
| Works with the visitor's assistive technology, unchanged | ||
| Plain-language explanation of each issue | Limited | |
| AI code-level fix suggestions | ||
| Compliance reports (EAA / WCAG 2.2 AA) | Varies | |
| Draft VPAT generation | ||
| Remediation audit trail (proof of work) | ||
| Adds third-party JavaScript to your site | Yes (a downside) | No |
| Continuous monitoring & regression alerts | Varies |
Why overlays don’t make you compliant
An overlay runs in the visitor’s browser and patches the rendered page - it never touches your source. That creates three problems. First, it only addresses issues a script can detect and safely auto-correct, which is a fraction of WCAG. Second, assistive-technology users frequently report that overlays conflict with their own screen reader or keyboard setup, making sites harder to use. Third, because nothing in your codebase changed, you have no durable evidence of remediation to show if you receive a demand letter.
What real remediation looks like
AllyProof scans your pages with axe-core, HTML_CodeSniffer, and APCA contrast analysis, then gives you a plain-language explanation and an AI code-level fix for each violation. You change the underlying HTML, CSS, or components, re-scan to confirm, and keep a full audit trail of what was fixed and when. That trail - plus exportable EAA / WCAG 2.2 AA reports and a draft VPAT - is what demonstrates a good-faith, documented effort. Automated testing covers roughly 57-70% of WCAG criteria; the rest needs manual expert review, which no overlay provides either.
The honest caveat
No tool can guarantee legal compliance, and AllyProof doesn’t claim to - be wary of any product that does. What AllyProof gives you is the fastest path to actually fixing your accessibility issues and the documentation to prove you did.
Scan your site free
See the real WCAG violations on your site in under a minute - no card, no widget to install.
Start freeFrequently asked questions
What is an accessibility overlay?+
An accessibility overlay (or widget) is a piece of third-party JavaScript you add to your site that tries to detect and modify accessibility issues in the visitor's browser at runtime - for example, injecting alt text or adjusting contrast on the fly. It changes what the browser renders; it does not change your underlying code.
Do accessibility overlays make a website ADA or WCAG compliant?+
No. No tool - overlay or otherwise - can guarantee legal compliance. Overlays in particular have been the subject of thousands of lawsuits and, in 2025, an FTC action against overlay vendor accessiBe. They mask a subset of issues in the browser rather than fixing the source, and assistive-technology users frequently report that overlays make sites harder to use, not easier.
What does AllyProof do differently?+
AllyProof scans your site for WCAG 2.2 AA violations, explains each one in plain language, and generates AI-powered code-level fix suggestions so you fix the actual source. It also produces exportable compliance reports, draft VPATs, and a full remediation audit trail - the documentation that demonstrates a good-faith effort. Automated scanning detects roughly 57-70% of WCAG criteria; full conformance still requires manual expert review.
Is AllyProof an overlay?+
No. AllyProof never injects a widget onto your site or modifies your pages at runtime. It's a scanning, remediation, and monitoring platform that helps your team fix the code and prove the work.
Can I keep my overlay and use AllyProof too?+
You can, but the point of AllyProof is to make the overlay unnecessary. Use AllyProof to fix the underlying issues; once the source is accessible, you no longer depend on a runtime widget that assistive-technology users may disable or distrust.