Honest comparison

A real audit vs an overlay widget

Accessibility overlays promise instant compliance from a single line of JavaScript. Courts and the disability community disagree - overlays have been named in hundreds of lawsuits because they do not fix the code underneath. A real audit finds the issues and writes the fixes you actually apply.

What overlays are good for

A few user-facing preference toggles (font size, contrast theme) are a genuinely nice convenience. The problem is selling that script as legal compliance - it does not fix the underlying barriers, and regulators and courts have said so repeatedly.

What an audit gives you

A prioritized list of the real barriers, written for a business owner, plus ready-to-paste corrected markup, ARIA, alt text and contrast CSS - in a white-label PDF you resell. Fix it once, in the code, and it stays fixed.

Feature by feature.

Reportiv audit compared with Overlay widget, feature by feature
Feature	Reportiv audit	Overlay widget
Fixes the underlying code	Yes: Produces corrected markup, ARIA, alt text and contrast CSS to paste into the codebase	No: Layers a script on top; the source code stays inaccessible
Legal standing	Yes: Helps work towards WCAG 2.1 AA / EAA conformance by fixing the real issues	No: Named in hundreds of US accessibility lawsuits; widgets are not a defense
Who does the work	Yes: Your developer pastes a one-time fix; the page is genuinely better	Partly: An automated script tries to patch at runtime, often breaking screen readers
Ongoing cost	Yes: Audit on a subscription; fixes are permanent once applied	No: Recurring per-domain fee forever, or the patch disappears
Client deliverable	Yes: White-label PDF report your agency resells under its own brand	No: A third-party badge on the client's site
Honest about limits	Yes: Clearly states it is automated + AI-assisted, not a legal certification	No: Often marketed as instant compliance - the core of the lawsuits
Performance impact	Yes: None - fixes are static code changes	Partly: Adds a render-blocking script to every page load

Fixes the underlying code

Reportiv audit: Yes: Produces corrected markup, ARIA, alt text and contrast CSS to paste into the codebase
Overlay widget: No: Layers a script on top; the source code stays inaccessible

Legal standing

Reportiv audit: Yes: Helps work towards WCAG 2.1 AA / EAA conformance by fixing the real issues
Overlay widget: No: Named in hundreds of US accessibility lawsuits; widgets are not a defense

Who does the work

Reportiv audit: Yes: Your developer pastes a one-time fix; the page is genuinely better
Overlay widget: Partly: An automated script tries to patch at runtime, often breaking screen readers

Ongoing cost

Reportiv audit: Yes: Audit on a subscription; fixes are permanent once applied
Overlay widget: No: Recurring per-domain fee forever, or the patch disappears

Client deliverable

Reportiv audit: Yes: White-label PDF report your agency resells under its own brand
Overlay widget: No: A third-party badge on the client's site

Honest about limits

Reportiv audit: Yes: Clearly states it is automated + AI-assisted, not a legal certification
Overlay widget: No: Often marketed as instant compliance - the core of the lawsuits

Performance impact

Reportiv audit: Yes: None - fixes are static code changes
Overlay widget: Partly: Adds a render-blocking script to every page load

Audit a site against WCAG 2.1 AA.

Run a free audit - no credit card, a client-ready accessibility PDF in about five minutes.

Overlay vendors (accessiBe, UserWay, AudioEye and others) are trademarks of their respective owners; Reportiv is not affiliated with or endorsed by any of them. This page reflects widely reported litigation and accessibility-community guidance as of June 2026. Reportiv provides automated and AI-assisted analysis, not a legal conformity assessment or certification.