Skip to content
Barrierefrei²

Success criterion 3.2.6

3.2.6 Consistent Help

Level AUnderstandable

When support becomes a reliable companion.

1. What is the goal of this criterion?

Imagine standing in a huge shopping centre, desperately looking for the information desk – sometimes it’s at the main entrance, sometimes upstairs, sometimes hidden away completely. Frustrating, right? That’s how many people feel on websites when help features keep jumping around.

The goal of WCAG Success Criterion 3.2.6 is to turn help options into a reliable signpost. If your website offers contact details, live chat, FAQs or other support, they should sit at the same point in the sequence of content on every page – like a trusted companion who’s there when you need them.

The criterion is new in WCAG 2.2 and sits at Level A.

2. What exactly does it require?

Specifically, it’s about consistently placing four types of help mechanism when they’re repeated across several pages of a website:

Human contact details: phone numbers, email addresses, opening hours or postal addresses.

Human contact mechanisms: live chat, contact forms, messaging systems or social media channels.

Self-help options: FAQ sections, how-to pages, help sections or help centres.

Fully automated contact mechanisms: chatbots or other automated support systems.

The rule is simple: if one of these mechanisms appears on several pages of your website, it must appear in the same order relative to the rest of the page content. That doesn’t mean it has to be placed pixel-perfectly in the same spot – what counts is the order in the source code, i.e. the way a screen reader reads the page.

Important: the criterion doesn’t require you to offer help at all. It only applies if you do. The help mechanism can sit directly on the page or be reachable via a link to a page containing the information.

Exceptions only apply when the person initiates a change themselves – for example by zooming or rotating their device, which shows a different layout variant. Pages are always compared within the same variant.

3. Why does it matter for accessibility?

Imagine trying to fill in a complicated online form and simply not finding any help. You search and search – sometimes the “Contact” link is in the header, sometimes in the footer, sometimes tucked away in the sidebar. For many people, that quickly turns into a nightmare.

Consistently placed help supports accessibility because it:

  • helps people with cognitive disabilities find support without having to search from scratch every time.
  • lets people with visual impairments reach help options quickly because they know where they are.
  • makes it easier for people with attention or memory difficulties to find help again without exploring the page anew each time.
  • takes the edge off stressful situations where help is needed fast – such as important tasks or time pressure.

And last but not least: consistency reduces mental effort for everyone and makes websites more predictable and trustworthy.

4. How to meet the criterion

Technically, this is usually straightforward, but it takes a well-thought-out content strategy. Here are some proven tips:

Identify your help mechanisms:

  • Take stock: what kinds of support do you offer?
  • Choose a fixed location: in the header, the footer or as a persistent element?
  • Keep a consistent order: e.g. phone first, then email, then live chat.

Keep the order stable:

  • Use templates or a design system to ensure consistent placement.
  • Make sure the order stays the same across all pages within each layout variant.
  • Test different zoom levels and orientations – help should be reliably findable in every view.

Use clear labels:

  • Pick one label such as “Contact”, “Help” or “Support” – and stick with it.
  • Icons and text should always look and work the same (see Consistent Identification).
  • Avoid confusing variations like “Help”, “Support” and “Get in touch” for the same thing.

Alternative: the central help hub

  • Place a single “Help” link consistently on every page.
  • Have it lead to a central page with all your support options.
  • This simplifies implementation and gives you more flexibility.

Technical implementation:

  • Put help mechanisms into reusable header or footer modules in your CMS.
  • Watch the source order – CSS Grid or Flexbox may adjust the look but shouldn’t change the sequence from page to page.
  • Embed a chat widget at the same point in the source code on every page.

Closely related is Consistent Navigation. If you want to go further, offer context-sensitive help as described in Help.

5. Why this criterion matters for businesses

With Success Criterion 3.2.6, too, accessibility isn’t an end in itself – it brings tangible benefits for your business.

1. Fewer drop-offs

Consistently placed help lowers the barrier to actually seeking support instead of giving up. Especially for older people or in stressful situations, predictability is a real boost to trust.

2. More efficient support

When people quickly find the right help, vague enquiries go down. Your support team can focus on real problems instead of guiding people around the website.

3. Customer satisfaction and brand trust

A website that works reliably comes across as professional. People who know they’ll find help quickly if something goes wrong are more willing to tackle complex tasks or purchases.

On the legal side: 3.2.6 is new in WCAG 2.2. The harmonised standard EN 301 549, which the European Accessibility Act and its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG), rely on, currently refers to WCAG 2.1 Level AA for web content – so 3.2.6 isn’t explicitly required there yet. Because it’s easy to implement and WCAG 2.2 is the current W3C standard, it’s still well worth doing. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.2.6 Consistent Help (Level A)

If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web 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:

  • Human contact details;
  • Human contact mechanism;
  • Self-help option;
  • A fully automated contact mechanism.

Note 1: Help mechanisms may be provided directly on the page, or may be provided via a direct link to a different page containing the information.

Note 2: For this success criterion, “the same order relative to other page content” can be thought of as how the content is ordered when the page is serialized. The visual position of a help mechanism is likely to be consistent across pages for the same page variation (e.g., CSS break-point). The user can initiate a change, such as changing the page’s zoom or orientation, which may trigger a different page variation. This criterion is concerned with relative order across pages displayed in the same page variation (e.g., same zoom level and orientation).

In short: if your website offers contact details, contact options, self-help or a chatbot on several pages, they always appear in the same order relative to the rest of the content.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 3.2.6 (opens in a new tab)