Skip to content
Performance & Accessibility

Consistent Help: The Decisions That Matter

Placing help mechanisms, such as contact details, chat, a help page link or a self-help option, in the same place on every page where they appear.

Marcus Adeyemi Technical Director 2 min read 21 views
Consistent Help: The Decisions That Matter

Why does it matter?

People who need help should not have to search for it on each page, and WCAG 2.2 made consistent placement of help a level A requirement.

What are the numbers?

  • WCAG 3.2.6 Consistent Help, A help mechanisms repeated across pages appear in the same relative order
  • Covered mechanisms human contact details, contact methods, self-help options and automated contact such as chatbots
  • Not required providing help; the rule applies when help is offered
  • Added in WCAG 2.2

What should I do?

  1. Place help and contact links in the same spot in every template
  2. Keep chat launchers in a consistent position
  3. Include help within multi-step processes
  4. Label help links clearly
  5. Check help placement on mobile layouts
What to do and what to avoid with consistent help, side by side
Good practice against the usual mistakes, from the sources listed below.

What should I avoid?

Avoid:

  • Contact links that move between header and footer
  • Help available on some steps of a form but not others
  • Chat widgets that appear in different places
  • Help hidden behind unclear icons

When should I get help?

Short answer Bring in help when support options vary across sections of a site, or when adding chat or help widgets.

Where this comes from

The figures and practices above come from the sources listed.

Working on something like this?

We take on Performance & Accessibility work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.

Where to go next

Spotted something wrong? Report an error on this page. We correct on the page and say what changed.

All services

The work behind this article, and what it costs.

Marcus Adeyemi

Builds and maintains the web work. Writes about front-end architecture, performance, accessibility and the unglamorous parts of keeping a site alive.

Keep reading

More in Performance & Accessibility