- Level
- A
- Since
- WCAG 2.2
3.2.6 Consistent Help
Where a site offers help, such as contact details, a contact form, a help page or a chatbot, it must sit in the same place relative to the rest of the page on every page that has it.
/ What it requires
People with cognitive and learning disabilities often cannot finish a task without help, and hunting for that help uses up the energy they need for the task itself. This criterion covers four kinds of help: human contact details, such as a phone number or an email address; a human contact mechanism, such as a chat or a contact form; a self-help option, such as an FAQ or a support page; and a fully automated contact mechanism, such as a chatbot. When one of them is repeated on several pages of a set of web pages, it has to come in the same order relative to the other page content each time. A direct link to a page holding the help counts as the help.
Order means the serialized order of the page, the sequence in which it is read, not its pixels. W3C notes that a help item shown elsewhere on screen but kept in the same order does not fail, though it helps nobody. The criterion does not require a site to offer help, nor help on every page, nor help inside PDFs and other downloadable documents. A change the user starts, such as zooming or turning the device, may move the help, and pages are compared in the same variation. Moving between pages or signing in does not count as such a change, unless signing in leads to a distinct set of web pages.
This criterion is new in WCAG 2.2 and is not part of WCAG 2.0 or 2.1.
/ How pages fail it
- The contact phone number sits in the header on most pages and only in the footer on product pages.
- A Help link comes before the main menu on the home page and after the search box on inner pages.
- The chat launcher comes before the page content in the source of some templates and after the footer in others.
- The checkout moves the link to the FAQ from the header to the end of the form, while every other page keeps it at the top.
- A landing page built with another tool repeats the contact details but places them in a different position relative to the menu and the main content.
/ How to check it yourself
- Find the help the site offers: contact details, contact forms or chat, help or FAQ pages and chatbots. Note on which pages each one appears.
- For the pages that carry the same help item, note what comes before and after it: header, menu, main content, footer.
- Check the serialized order rather than the picture. Tab through the page, read it with a screen reader such as NVDA, or inspect the DOM order in the developer tools.
- Compare the pages at the same zoom and orientation. Then switch to a phone width and compare the phone layouts with each other.
- Include the pages behind a login and the checkout, which are often built from separate templates.
/ How to fix it
- Render the contact details, the help link and the chat launcher from the shared header or footer component, not page by page.
- Insert a chat widget at the same point of the DOM on every page, for example as the last element of the footer, and do not move it per template.
- When a page in a flow such as the checkout drops the full header, keep the help link in the same relative position, for example right before the main content.
- Keep the help items in the same DOM order on every page of one layout, and do not shift them with the CSS order property on some pages only.
- Point every help link to one help page, so the item stays the same even when the content behind it changes.
/ What our scanner checks
Nothing in our automated scan checks this. It is a question about the same item across many pages, and our rules read one page at a time. The bundled HTML_CodeSniffer standard is WCAG 2.1 AA and has no test for this 2.2 criterion. In a manual audit a person records where each help item sits on a sample of templates and compares the order.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Does WCAG 2.2 require every page to have a help link?
No. 3.2.6 does not require help at all. It applies when a site offers one of the listed help mechanisms on several pages, and then asks that it appears in the same order relative to the rest of the content. A page that has no help mechanism does not fail.
Does a chatbot count as help under 3.2.6?
Yes. The criterion names four kinds: human contact details, a human contact mechanism, a self-help option and a fully automated contact mechanism. A chatbot is the fully automated one. If it appears on several pages, it has to keep the same relative order on each, like a phone number or a link to the help page.
What level is Consistent Help?
Level A. It is one of the criteria added in WCAG 2.2, so an audit against WCAG 2.1 does not include it. Because it is level A, it is part of every conformance claim against WCAG 2.2, at level A and at level AA.
