Skip to main content
Crayons and Code

Sold an accessibility overlay?

Overlays sit on top of your site. They leave the underlying problems in place.

Overlays and widgets promise fast accessibility. They do not change your underlying code. WebAIM found 67% of practitioners rate overlays “not at all” or “not very” effective, rising to 72% among respondents with disabilities. EDF and IAAP warn overlays interfere with assistive technology and override user settings.

What overlays are

A third party script injects an extra interface into your pages.

You get a floating button with controls for text size, contrast, fonts, and similar toggles.

Some vendors claim automated “AI remediation”.

Red flags in sales pitches

Why they fail

Accessibility relies on structure, semantics, content quality, and predictable behaviour.

Overlays do not fix those fundamentals.

What I do instead

I prioritise fixes that remove blockers in real journeys.

Evidence and sources

This topic attracts strong marketing claims.

This page links to primary and disability-led sources.

Relevant work

Rough pricing

This work usually falls into one of these routes:

If your site needs deeper changes than fixes allow, you will get a clear steer.

See accessibility services Start a new project

FAQs

Do overlays make a site WCAG compliant?

No. They do not fix the underlying code and content. They often add new barriers.

Do overlays help screen reader users?

Not reliably. Screen readers depend on correct semantics, labels, roles, and states in the underlying interface.

What is the fastest route to improvement?

Pick high value journeys. Fix the biggest blockers. Roll fixes into shared components. Retest.

Availability

Next full project start: January 2026.
Small jobs: 3 to 7 days. Capacity: up to 14 hours per week.