Notes on overlay risk and the evidence
How accessibility overlays interact with ADA/WCAG claims, how to read a before/after diff, and what the witness actually captures.
Why accessibility overlays don't stop ADA lawsuits
Overlay vendors promise a one-line script will make a site compliant. The demand letters keep arriving anyway. Here is the gap between the marketing claim and what an automated check actually sees.
Read the postWebsite Accessibility Scores and Google Lighthouse: What a 0–100 Number Can Show — and What It Still Can't Prove
A Google Lighthouse accessibility score can summarize automated findings, but it is not a WCAG verdict or dated page-level evidence from a live route. Here is what the number can show, what it can hide, and where proof begins.
Accessibility guarantee vs independent evidence: what site owners should keep
A vendor guarantee, badge, or accessibility statement is not the same thing as independent evidence. Here is the practical record a site owner should keep when an overlay is part of the stack.
accessiBe vs a manual audit: what each actually proves for ADA compliance
Is accessiBe enough for ADA compliance? The honest answer depends on what "enough" means to a plaintiff, a judge, or your own risk tolerance. Here is what each approach actually proves — and what it cannot.
What to Do When You Get an ADA Website Accessibility Demand Letter
An ADA website accessibility demand letter lands in your inbox. Before you respond, you need evidence — not assurances from your overlay vendor. Here is what to do, in order.
A WCAG 2.2 AA checklist for sites running an accessibility overlay
A practical WCAG 2.2 AA checklist accessibility overlay operators can use: understand what automated axe-core testing covers, which criteria require manual review, and where overlays reliably fall short.
Does the UserWay widget actually make your site WCAG compliant?
Does UserWay make a site WCAG compliant? We break down exactly what the widget can and cannot change at runtime — and how a two-pass axe-core test shows you where the gap is.
Reading an axe-core before/after diff
A witness run produces two axe-core result sets — overlay off and overlay on — and a per-rule diff between them. Here is how to read that diff and what each transition tells you.
How Accessibility Overlays Conflict With Screen Readers
Accessibility overlay screen reader conflicts are real and measurable at the DOM level. This post explains what overlays inject, where ARIA collisions occur, and what automated tooling can and cannot tell you.
What a Risk Packet contains
The free witness shows one finding. The $49 Risk Packet is the full evidence file for 5–10 high-risk pages. Here is exactly what is inside and why each piece is there.
How to document website accessibility evidence that holds up
Learn how to document website accessibility evidence that survives a legal challenge or procurement audit — reproducible test runs, timestamps, snapshot hashes, and claims quoted back against observations.
Drift monitoring: why a passing scan today can fail next month
Accessibility is not a one-time state. Overlays update, pages get redeployed, and a rule that held up in June can fail in July. Drift Monitor re-runs the witness on a schedule and tells you when something moves.
Writing an accessibility statement when you use an overlay
Accessibility statement best practices change when a third-party overlay is in the picture. An overly broad claim can create more legal exposure than no statement at all — here is how to write one that holds up.
Running OverlayRiskWitness from the MCP server
OverlayRiskWitness ships as a Model Context Protocol server, so an AI agent can run a witness, read findings, and trigger a packet without leaving its toolchain. Here is the setup.
ADA Compliance for Ecommerce Checkout: What Overlays Miss and How to Gather Evidence
ADA compliance for ecommerce checkout flows matters most where money changes hands. This guide covers keyboard access, form labels, focus order, and how to collect timestamped before/after evidence your overlay may be missing.
White-label accessibility monitoring for agencies: a recurring revenue model built on evidence
White-label accessibility monitoring for agencies turns a one-time compliance audit into a subscription offering — with timestamped, vendor-independent evidence your clients can actually act on.
Using AI agents to test website accessibility over MCP
AI agent website accessibility testing is now a single tool call away. Here is how OverlayRiskWitness exposes its two-pass axe-core witness over the Model Context Protocol — and what a real tool response looks like.