Why Must Support Stay in a Consistent Location? WCAG 2.2 Consistent Help for Enterprise Websites

Consistent Help does not require a website to provide a customer-service telephone number. It requires that when mechanisms such as customer support, chat, FAQs and self-service help recur across pages, they retain a consistent relative position or order so users do not need to find them again each time.

On many websites, “help” seems to be everywhere: chat appears in the bottom-right corner of the homepage, the checkout page hides it behind a question mark at the top, a form puts the support number in the footer, and mobile buries it in a third-level menu. An experienced user may spend only a few extra seconds looking, but repeatedly searching for help substantially raises the cost of a task for users with cognitive disabilities, attention difficulties or anxiety about the problem they are trying to solve.

01 The conclusion: WCAG 2.2 requires a consistent order for repeated help mechanisms

If the same help method appears across a set of pages, it should remain in a consistent relative order. The criterion does not force you to provide help, but once a mechanism is provided repeatedly, do not move it on every page.

02 1. What counts as a Help Mechanism?

W3C examples include human contact details, human contact mechanisms, self-help options and fully automated contact mechanisms. In real products, this can mean telephone or email, live chat, a Help Center, FAQs, support tickets or an AI assistant. The defining characteristic is that the mechanism helps users complete or resolve the current task.

03 2. Why is a fixed chat button in the bottom-right corner not always enough?

If chat is fixed on desktop but moved deep into a mobile menu, or the payment page replaces it entirely with a telephone entry point for conversion reasons, users still have to relearn the interface. The design system should define stable locations for help across breakpoints and critical flows, along with the pages where reasonable exceptions apply.

04 3. Consistent Help does not mean duplicating many contact methods on every page

The criterion is about predictability, not redundancy. A site can provide one global Help entry point, then offer chat, telephone and documentation based on context after it opens. Contextual help can be added at a high-risk step without removing or disrupting the established global entry point.

05 4. Long forms need contextual help and global help at the same time

For example, a “What is this?” explanation can appear beside the Tax Registration Number field in a corporate qualification application, while customer support or the Help Center remains available in its fixed page location. The local explanation solves a field-level question; global help supports users who cannot continue. The two levels should not replace one another.

06 5. AI support is also a help mechanism and should not suddenly become mandatory

More companies now direct users to AI first, then escalate to a human. Users should understand clearly that the help is automated and know how to reach a person when necessary. For complex complaints, account security, payment and similar issues, an endlessly looping bot significantly reduces usability and trust.

07 6. Keep help entry labels consistent

Calling the same feature “Support,” “Contact an Advisor,” “Customer Service Center” and “Questions?” on different pages increases recognition costs. Tone can reflect the brand, but the name and icon for the primary entry point should carry stable semantics. In particular, do not make users guess the meaning of an unlabeled question mark.

08 7. How to implement it in a design system

• Define the fixed location of the global help entry point on desktop and mobile.
• Define available channels and their display priority.
• Specify when contextual help can be added.
• Design AI-to-human escalation as a formal state.
• Require accessibility and support-team review for variants in critical flows.

09 Finally: when users most need help, they usually have the least patience for finding it

The value of Consistent Help is simple: learn the location once and find it again later. When corporate websites and complex SaaS products provide this stability, they improve cognitive accessibility while reducing interruption and abandonment during critical flows.

10 8. Help content should remain contextually consistent

The same help entry point can prioritize content related to the current page—for example, showing payment FAQs first on a payment page—while keeping its name, location and return behavior stable. This preserves predictability without limiting every page to an isolated set of help content.

11 9. Measure success in finding help, not the number of chats opened

A high number of chat openings may indicate that the page itself is difficult to use. Examine the time from an error or critical step to finding help, first-contact resolution, repeated contacts and reasons for human escalation. The purpose of a help mechanism is to reduce blockage, not increase bot conversation volume.

12 10. Help must remain accessible under zoom, reflow and keyboard use

A fixed bottom-right button is not reliable if it covers a form button at 200% Zoom, is obscured by a Cookie Banner, or can be activated only with a mouse. Test text magnification, narrow-screen reflow, keyboard focus and screen-reader names so that consistent location does not create obstruction.

Help mechanisms should ideally not depend on hover to appear, because touch and keyboard users may be unable to trigger the same state.

Frequently Asked Questions

Does WCAG 2.2 require every website to provide customer support?

No. SC 3.2.6 primarily requires repeated help mechanisms to maintain a consistent order.

Does fixing a chat button in the bottom-right corner guarantee conformance?

No. It must remain predictable across the set of pages and responsive states, and it must work with a keyboard and screen reader.

Does an FAQ count as a Help Mechanism?

If it is a self-service help entry point that assists users in completing a process, it can be part of the consistent help mechanism.

Can an AI chatbot replace human support?

The criterion does not directly prescribe business channels, but high-risk or complex problems generally need a clear escalation path so users are not trapped in automation.

Must field-level hints appear in the same location on every page?

Consistent Help mainly addresses repeated global or general help mechanisms. Field-level explanations should remain close to the relevant control.