Consistent Help: Keep Support in the Same Place
Also called: Consistent help location, Help mechanism, Findable support
Definition
Consistent Help is WCAG success criterion 3.2.6. If help mechanisms such as contact details, a contact form, a self-help page or a chatbot are repeated on multiple pages of a site, they occur in the same order relative to other page content, unless the user changes it.
Consistent help means that the ways to get support on your website – a phone number, a contact link, a chat, an FAQ – sit in the same place on every page where they appear. People who get stuck should not have to search for help again on each page. WCAG 2.2 makes this a Level A requirement.
What it means
WCAG 3.2.6 Consistent Help is a Level A criterion, new in WCAG 2.2. If a web page contains one of the help mechanisms below, and those mechanisms are repeated on multiple pages within a set of web pages, they occur in the same order relative to other page content – unless a change is initiated by the user.
| Help mechanism | Typical example |
|---|---|
| Human contact details | Phone number, email address, opening hours |
| Human contact mechanism | Contact form, live chat with staff, messaging link |
| Self-help option | FAQ, help center, "How do I …" page |
| Fully automated contact mechanism | Chatbot |
"Same order" means the order in the code – how the page is read from top to bottom – not the exact pixel position. A help link may move visually between a phone and a desktop layout; the criterion compares pages in the same variation, such as the same zoom level and orientation. Help can be on the page itself or behind a direct link.
W3C names who benefits: people who have difficulty locating help, including people with cognitive and learning disabilities. A user who finds help once knows where to look next time.
Examples
<footer>
<nav aria-label="Footer">
<a href="/shipping">Shipping</a>
<a href="/returns">Returns</a>
<a href="/help">Help center</a>
<a href="/contact">Contact us</a>
</nav>
<p>Call us: <a href="tel:+18005550199">1-800-555-0199</a> (Mon–Fri, 9 am–5 pm)</p>
</footer>Built once in a shared footer template, the help links come in the same order on every page. A content management system such as WordPress usually does this through its theme – problems start when a landing page, the shop or the checkout uses its own layout.
Put help in a shared header or footer template, keep the order of help links the same on all pages, show opening hours with a phone number, and use the same chat position throughout the site.
Move the contact link from the header to the footer on product pages, drop the help link only during checkout while it shows elsewhere, or change the order of "Help" and "Contact" between page templates.
How to check consistent help
Questions
What counts as a help mechanism in WCAG 3.2.6?
Four kinds: human contact details such as a phone number or email address, a human contact mechanism such as a contact form or live chat, a self-help option such as an FAQ, and a fully automated contact mechanism such as a chatbot.
Does help have to be in exactly the same spot?
Not to the pixel. W3C means the same order relative to other page content, as the page is read. Visual position can differ between layouts, such as phone and desktop.
Does consistent help apply to PDF files?
No. W3C says PDFs and other documents downloaded from a site are not part of that set of web pages, so 3.2.6 does not apply to them.
Is my website failing if it has no contact page?
Not under this criterion. Consistent help does not require help to exist. It only applies when a help mechanism is repeated across pages.
Related terms
Redundant Entry: Don't Ask for the Same Data Twice
Redundant Entry is WCAG success criterion 3.3.7. Information a user already entered or was given in the same process must be auto-populated or available to select when it is needed again – unless re-entry is essential, needed for security or the information is no longer valid.
Read definition: Redundant Entry: Don't Ask for the Same Data TwiceAccessible Authentication: Logins Without Memory Tests
Accessible Authentication (Minimum) is WCAG success criterion 3.3.8. No step of a login may require a cognitive function test – remembering a password, transcribing a code, solving a puzzle – unless an alternative, a helping mechanism or an allowed exception is available.
Read definition: Accessible Authentication: Logins Without Memory TestsError Suggestion: Help Users Fix Form Errors
Error suggestion means that when a website detects an input error and knows how it could be corrected, it offers that correction to the user. WCAG 3.3.3 requires it at Level AA, unless it would jeopardize security or the purpose of the content.
Read definition: Error Suggestion: Help Users Fix Form Errors