Troubleshooting

Widget not appearing on localhost or a staging environment — the AccessiLens widget is designed to initialise on all environments including localhost, staging, and development domains. These do not count toward production domain limits. If the widget is not rendering, check that the script tag was saved to the correct template file and that your browser cache has been cleared (hard reload: Ctrl+Shift+R or Cmd+Shift+R).

Widget hidden behind another element (z-index conflict) — if the accessibility toolbar is obscured by a chat widget, cookie banner, or sticky header, add window.AccessiLensConfig = { zIndex: 99999 } to your page before the AccessiLens script tag. This sets the widget's CSS z-index to ensure it renders above all other positioned elements.

Widget not loading after a CDN-cached deployment — if you use a CDN (Content Delivery Network) such as Cloudflare, Fastly, or AWS CloudFront to serve your pages, the CDN may be serving a cached version of your HTML that does not yet include the new script tag. Log into your CDN's dashboard and perform a full cache purge (sometimes called 'cache invalidation'). The updated page — with the AccessiLens script — will then be served on the next request.