Real audit · no theater

A site running a popular accessibility overlay widget — still had 50 WCAG failures it never fixed.

We scanned a live production site that had a well-known "one-line accessibility overlay" installed. CloviAble ran axe-core + Lighthouse against it. Here's what the overlay didn't catch.

real WCAG failures (serious + moderate)

49/50

failing elements that carry the overlay's own injected attributes — the widget is right there, and they still fail

25/100

Lighthouse performance — the overlay adds weight, doesn't fix speed

The tell: 49 of the 50 failing elements carry the overlay's injected markup. The accessibility widget is literally on the elements that fail the checks. An overlay injects a toolbar; it does not remediate your HTML.

Issue	WCAG	Severity	Count	What it means
Color contrast	1.4.3 AA	serious	25	Text fails the 4.5:1 contrast minimum
Target size	2.5.8 AA	serious	20	Tap targets too small on mobile
Heading order	1.3.1 A	moderate	5	Heading levels skipped — breaks screen-reader structure

Overlays sell the feeling of compliance. CloviAble finds the real issues — every failure mapped to its WCAG criterion, its exact selector, severity, and the fix — so the page actually becomes accessible. Real accessibility. No theater.

Scan your site free →

Methodology: CloviAble runs axe-core (~50 WCAG checks) + Lighthouse, keyless, against the rendered page. Counts above are from a single real production audit (2026-06-15). We don't name the audited site or the overlay vendor. Note: axe surfaces a different subset than a manual audit — the honest headline is "50 real, fixable failures + a performance problem the overlay made worse."