what-overlays-promise
An accessibility overlay is a third-party JavaScript widget you add to a website with a single script tag. It promises to make the site accessible automatically: enlarging text, adding alt text with AI, forcing keyboard focus, adjusting contrast. Vendors sell it as instant WCAG compliance — often with an "accessibility shield" badge to display in the footer.
The pitch lands well with small agencies and their clients: no developer time, no redesign, $49/month instead of a five-figure audit. The problem is not that overlays do nothing. It is that what they do does not match what they claim — and in 2026 both regulators and courts have said so.
🤖 AI-powered auto-fixes
Overlays claim to detect and fix accessibility issues at page load. Automated detection catches only a fraction of WCAG failures, and many "fixes" (auto-generated alt text, DOM rewrites) break screen reader behaviour.
🛡️ Compliance badges
Vendors let sites display a certification-style badge implying legal protection. No badge confers compliance — only conformance with EN 301 549 / WCAG 2.1 AA does.
💸 Recurring cost
A typical agency pays $49–$149 per month per site. Over three years that is more than a one-off professional remediation of most small business sites.
eaa-position
For agencies working in the EU, the relevant law since 28 June 2025 is the European Accessibility Act. It requires e-commerce, banking, transport, and other covered services to conform with EN 301 549 — which incorporates WCAG 2.1 AA — and to publish an accessibility statement. Market surveillance authorities can require corrective action; member state penalty frameworks include fines up to €3 million in some countries.
The European Commission has stated that overlays alone do not achieve EAA compliance, and consumer organisations including the European Disability Forum have issued statements against marketing them as such. An overlay cannot fix the structural issues the EAA targets: missing keyboard support in checkout flows, inaccessible documents, unlabeled form fields in booking systems. Those require code changes.
The practical position for a small agency is simple: an overlay installed on top of a non-conformant site leaves the site non-conformant. The money is spent, the statement cannot honestly be published, and the underlying risk remains.
what-works
None of this means automated tools are useless. It means they belong in the right place: detection, not remediation. Run a scanner to find issues, then fix them in the code. That workflow costs nothing extra and produces a site that actually conforms.
A realistic plan for a small agency portfolio:
• Scan every client site for the common automated-detectable failures (missing alt text, unlabeled inputs, contrast, heading structure).
• Fix those in templates and components once — every page on the theme benefits.
• Test keyboard navigation and one screen reader pass on critical flows (checkout, contact, signup).
• Publish an honest accessibility statement per site.
• Re-scan after content updates or new plugins.
This takes hours per site, not months — and unlike a widget subscription, it ends. When you can show a clean scan and a documented process, you can also price it as a service line instead of paying for a badge.
🔍 Scan first
Our free scanner checks 15+ WCAG rules on any URL — WordPress, Shopify, Webflow, or hand-written HTML. No install, no account.
🧩 Fix at template level
Most errors repeat across pages because they live in the theme. One component fix removes hundreds of findings.
📝 Document honestly
An accessibility statement based on real scan results protects you far more than an overlay badge ever did.