Accessibility Overlays Keep Failing. The Pattern Is the Point.

Corpowid's accessibility statement uses the phrase "substantially conformant." Not conformant. Not WCAG 2.1 AA compliant. Substantially conformant — a phrase that appears nowhere in WCAG success criteria (opens in new window) and exists primarily to sound reassuring while committing to nothing legally enforceable.

That single word is the tell. And it surfaces the same pattern that accessibility researcher Adrian Roselli has documented across six overlay vendors since 2020: these products don't solve accessibility problems. They add a layer of legal-sounding language over unresolved technical failures, and they charge organizations for the privilege.

What Corpowid and Skynet Technologies Actually Do

Roselli's September 2026 analysis documents two vendors in detail. The findings aren't subtle.

Corpowid introduces visible WCAG violations when its overlay activates. At 1,280px viewport width, zoomed to 200%, the page produces overlapping text, a horizontal scrollbar, and animation that pulses continuously. WCAG 1.4.4 (Resize Text) (opens in new window) requires text to be resizable up to 200% without loss of content or functionality. WCAG 2.3.1 (Three Flashes or Below Threshold) (opens in new window) addresses flashing content. Both criteria exist because real people — people with low vision, people with photosensitive epilepsy — are harmed when they're violated. An overlay that creates these conditions isn't a compliance tool. It's the problem.

Corporwid's accessibility statement compounds this with what Roselli accurately calls "squishy terms": substantially conformant, informed by, remain usable, we aim to respond. Each phrase is engineered to sound like a commitment while avoiding one. Organizations relying on this language for their own compliance posture are building on sand.

Skynet Technologies presents a different but equally instructive failure. The company doesn't deploy its own overlay on its own website — a detail that should stop any procurement conversation cold. When Roselli found it on a third-party restaurant site, the overlay demonstrated a feature that converts all text to ASL fingerspelling glyphs. The intent, presumably, was to serve Deaf users. The execution: the overlay applies the same American Sign Language alphabet regardless of whether the interface language is set to British English or Australian English — both of which use entirely different signing systems (BSL and Auslan, respectively). What was marketed as inclusive became a localization failure that excludes the communities it claimed to serve.

The overlay also introduces WCAG violations in its own interface, including issues detectable by automated scanners — the lowest bar in accessibility testing. As our research on automated testing methodology documents, automated tools catch at most 37% of real accessibility barriers. When an overlay fails that threshold in its own UI, the gap between marketing claims and technical reality is not a matter of nuance.

Why This Pattern Keeps Repeating

Roselli's archive now spans six vendors across six years: accessiBe (2020), UserWay (2021), FACILiti (2022), AudioEye (2023), Accesstive (2025), and now Corpowid and Skynet Technologies (2026). The consistency isn't coincidence.

The overlay market exists because ADA Title III (opens in new window) compliance creates real organizational pressure, and overlays offer a fast, low-cost answer to that pressure. The problem is structural: overlays operate on the rendered DOM, applying JavaScript-based modifications after a page loads. They cannot fix inaccessible underlying code, missing semantic structure, or absent alternative text in a way that assistive technologies reliably interpret. They can suppress some automated scan findings while leaving — or creating — barriers that affect actual users with disabilities.

This is the compliance framework paradox in action. As our analysis of multi-standard compliance documents, organizations under pressure from overlapping legal requirements often reach for solutions that appear to satisfy standards without actually doing so. Overlays are the extreme case: a product category that markets itself as the answer to WCAG conformance while being technically incapable of delivering it.

The legal exposure is real and documented. Settlement agreements in accessibility litigation increasingly include provisions that prohibit overlay-only remediation strategies, precisely because courts and the DOJ have seen this pattern. Our research on settlement implementation shows that organizations relying on surface-level compliance tools often face repeat litigation — the settlement doesn't solve the underlying access problem, so the harm continues.

What Organizations Should Do Instead

The practical alternative isn't complicated, though it requires more sustained effort than installing a script tag.

Start with an honest audit. Automated scanning identifies a fraction of WCAG issues. Manual testing with assistive technologies — screen readers, switch access, keyboard-only navigation — surfaces the rest. The Northeast ADA Center (opens in new window) provides guidance on evaluation methodology and can connect organizations with qualified evaluators. For higher education and transit contexts specifically, this means testing with the actual assistive technologies your users bring, not just the ones your IT department supports.

Fix the source, not the surface. Semantic HTML, proper heading structure, meaningful alternative text, sufficient color contrast, and keyboard accessibility are engineering decisions made at the code level. They cannot be reliably patched after the fact. WCAG 2.1 AA (opens in new window) provides the technical standard; Section 508 (opens in new window) applies the same technical baseline to federal agencies and their contractors.

Evaluate vendor claims against their own products. Skynet Technologies doesn't use its overlay on its own site. Corpowid's accessibility statement hedges every commitment. These are observable facts available before any contract is signed. Apply the same scrutiny to any accessibility vendor: does their product conform to the standards they're selling?

Build internal capacity. The compliance framework research consistently shows that organizations achieving durable accessibility outcomes invest in people — developers who understand semantic markup, designers who understand contrast and spacing, procurement staff who can evaluate vendor VPAT documentation critically. Overlays are appealing precisely because they seem to eliminate this investment. They don't. They defer it while adding risk.

The Honest Bottom Line

The overlay industry has had six years of detailed, public, technical criticism. The products have not substantively improved. The marketing language has gotten slightly more careful — Corpowid says "substantially conformant" rather than claiming full WCAG compliance — but the underlying technology hasn't changed in ways that matter to disabled users.

Organizations installing these tools aren't buying accessibility. They're buying the appearance of action. And as the litigation record shows, courts and the DOJ are increasingly capable of distinguishing between the two.

Disabled people deserve websites that work — not overlays that flash, scroll off-screen, and replace menu text with fingerspelling glyphs that don't correspond to the user's actual sign language. That's the standard. It's achievable with real engineering. No widget required.