When should we use an accessibility overlay on our website?

Do not rely on an accessibility overlay to make your website accessible; correct barriers in the underlying structure and validate the resulting experience. A widget or toolbar cannot substitute for accessible architecture, and promises of automatic compliance should not determine your approach.

Correct underlying barriers rather than mask them

An accessibility overlay adds a JavaScript widget or toolbar to a website, but it does not correct the underlying structure where accessibility barriers need to be addressed. Overlays typically address only a small percentage of WCAG failures, so their presence should not be treated as confirmation that a website is accessible.

Build accessibility into the website's architecture rather than treating it as a finishing layer. When assessing an overlay, distinguish the interface features it offers from the structural problems it leaves unresolved. Poor accessibility experiences can frustrate users, slow site performance and introduce legal risk.

In 2025, the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million over misleading accessibility claims, barring unsupported claims that its automated products can make any website WCAG-compliant or maintain compliance over time. Treat automatic-compliance promises as a reason for scrutiny, not a substitute for fixing the website.

Sources: The Prompt: Using AI to Create a More Accessible and Dynamic Digital Future