Accessibility overlay
An accessibility overlay is a JavaScript layer that can add user controls or modify the rendered page at runtime. Runtime behavior should not be treated as proof of WCAG, ADA, or EAA compliance.
Detailed explanation
Runtime accessibility products vary. They may add display controls, modify the rendered document, provide monitoring, or be paired with human services. Merchants should inspect the current product rather than infer every vendor’s behavior from the category label.
A runtime modification depends on the product’s script and does not by itself update a Shopify theme file. Merchants should test the experience before and after load, during script failure, with assistive technology, and alongside theme and third-party JavaScript.
In 2025 the FTC approved a final order requiring accessiBe to pay $1 million and restricting certain unsupported automated-conformance claims. The order concerns specified accessiBe conduct; it is not a blanket ruling about every runtime product or proof that source changes guarantee compliance.
How this applies to Shopify stores
AccessComply can apply eligible merchant-approved changes through supported Shopify theme and content paths. Theme edits remain only in the modified theme until overwritten and do not transfer automatically to another theme; extension behavior stops when the app or embed is removed.
What merchants should check next
Treat this term as a practical audit prompt, not just a definition. Check the storefront pages where the concept shows up in real customer journeys: product discovery, add-to-cart, cart drawer, checkout handoff, account login, and support contact flows. If the issue affects code, verify the rendered HTML and computed browser output after the theme change. If it affects copy or media, keep the merchant-facing wording accurate and easy to maintain.
Primary source: ftc.gov