Help mechanism not in consistent page location (WCAG 2.2 SC 3.2.6)
This check looks for a persistent, easy-to-find help or support link in the header or footer of every page, alongside any chat widget your site uses. This site has a chat widget installed, from a provider like Intercom, Drift, Crisp, Zendesk, Freshchat, HubSpot Chat, or Tidio, but no persistent help or support link was found in the global header or footer. This fails WCAG 2.2 Success Criterion 3.2.6, Consistent Help, a Level A requirement mandatory under the European Accessibility Act, because relying on a single chat widget as the only help option leaves visitors stranded if that widget fails to load, is blocked, or doesn't suit how they navigate. Your developer should add a consistent help or support link to the global header or footer used across every page template, so it doesn't depend on the chat widget alone. Budget around two hours to implement and check across templates.
Why this matters
This fails WCAG 2.2 Success Criterion 3.2.6, Consistent Help, a Level A requirement mandatory under the European Accessibility Act, because relying on a single chat widget as the only help option leaves visitors stranded if that widget fails to load, is blocked, or doesn't suit how they navigate.
How to fix it
Your developer should add a consistent help or support link to the global header or footer used across every page template, so it doesn't depend on the chat widget alone. Budget around two hours to implement and check across templates.