Verify consistent help
Description
This rule does not automatically validate anything. It simply reminds you to manually verify that help mechanisms (e.g., contact details, live chat, documentation links, FAQ pages) appear in the same relative order on all Web pages where they are present. It is based on WCAG 2.2 Success Criterion 3.2.6 Consistent Help (Level A).
When users navigate across pages in a set of Web pages (a collection of pages that share a common purpose and navigation), they build a mental model of where help is located. If help mechanisms move or change order between pages, users may waste time searching for assistance or miss it entirely. The rule scans for common help-related elements – such as <footer>, <header>, elements with class .help-widget or .support-link, and links whose href contains contact or help – and flags them for a manual review. No automated pass/fail determination is made.
Disabilities impacted
- Cognitive disabilities – People with cognitive or learning disabilities rely on predictable interfaces to avoid confusion and cognitive overload. When help mechanisms shift position unexpectedly across pages, they may be unable to locate assistance, causing frustration, task abandonment, or increased reliance on external support that could have been avoided with a consistent layout.
- Visual impairments – Screen reader users and people with low vision build spatial mental maps of page layouts. When help links or widgets appear in different positions on different pages, users must re-scan the entire page structure to find them, which is both time-consuming and disorienting – particularly when using keyboard navigation or screen magnification.
- Motor disabilities – People who use switch devices, eye-tracking, or other alternative input methods rely on predictable page landmarks to target interactive elements efficiently. If help mechanisms move, users who navigate sequentially or by spatial coordinates must expend additional physical effort and time to locate assistance, which can cause fatigue and increase the risk of input errors.
Why it matters
Consistent placement of help mechanisms is a foundational usability principle that supports all users, but is especially critical for people with disabilities. When help is predictably located, users can build procedural knowledge (knowing where to look) rather than relying on declarative memory (remembering what to look for). This aligns with the core WCAG principle of predictability, which states that Web pages must operate in ways users can anticipate.
Beyond accessibility compliance, consistent help placement reduces support ticket volume, improves user satisfaction, and strengthens brand trust. Organizations subject to legal requirements under the ADA, European Accessibility Act (EAA), or Section 508 of the Rehabilitation Act should treat this success criterion as a core requirement, not an optional enhancement. WCAG 3.2.6 became a Level A requirement starting with WCAG 2.2, meaning it is the most basic level of conformance and must be satisfied for any WCAG 2.2 claim.
Coding problems and solutions
Common coding problems
Since this rule is a manual-only reminder with no automated element validation, the following checklist describes what a human reviewer should manually verify when auditing for consistent help placement:
- Help mechanisms reordered between templates – Different page templates (e.g., product page vs. checkout) may include help elements in different positions within a shared header or footer, or even within entirely different page regions. A reviewer must compare the DOM order of help-related elements across all template types.
- Responsive layout reordering – CSS flexbox
orderproperties, grid placement, orfloat-based layout shifts can change the visual and DOM order of help items at different breakpoints. Verify that the relative order of help mechanisms remains stable across mobile, tablet, and desktop viewports. - Conditional help content – Some pages may show or hide help mechanisms based on authentication state, user role, or feature flags. A reviewer must check that when the same help mechanisms appear on multiple pages, they retain consistent ordering regardless of conditional visibility.
- Injected third-party widgets – Live chat buttons, AI assistants, or knowledge-base popovers injected by third-party scripts (e.g., Intercom, Zendesk) may render at arbitrary DOM positions or timestamps. These must be checked for consistent placement relative to native help elements.
- Single-page application (SPA) view changes – In SPAs, help mechanisms may be part of a shared shell component that is rendered only once, but client-side routing can swap adjacent content regions. Verify that the relative order of help elements within the shell does not shift when the surrounding content changes.
How to fix it
Define a shared help component
Include all recurring help mechanisms inside a single reusable component (e.g., a site-wide footer) that renders in the same DOM position on every page of the set.
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
<a href="/docs">Documentation</a>
<a href="/chat">Live chat</a>
</nav>
</footer><!-- Page A: footer links ordered by name -->
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
<a href="/docs">Documentation</a>
</nav>
</footer>
<!-- Page B: same links, different order -->
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/docs">Documentation</a>
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
</nav>
</footer>Preserve order across responsive breakpoints
Ensure that CSS layout changes (flexbox, grid, floats) do not alter the visual or DOM order of help mechanisms. If reordering is necessary for design reasons, maintain the same relative sequence.
/* Items stay in source order at all breakpoints */
.help-nav {
display: flex;
gap: 1.5rem;
}
@media (max-width: 768px) {
.help-nav {
flex-direction: column;
}
}/* Reorders items visually on small screens */
@media (max-width: 768px) {
.help-nav {
display: flex;
flex-direction: column;
}
.help-nav .chat-link {
order: -1; /* Chat moves to top, breaking relative order */
}
}Keep third-party widget containers stable
When embedding third-party help widgets (chat, knowledge-base popovers), place their mount points at a fixed location within a shared layout shell. Avoid injecting them dynamically at arbitrary positions.
<!-- Shared shell layout on every page -->
<header class="site-header">...</header>
<main id="main-content">...</main>
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
</nav>
<div id="help-widget-mount"></div><!-- fixed mount point -->
</footer>// Widget injected at body end, position varies per page
globalThis.setTimeout(() => {
const widget = document.createElement('div');
widget.id = 'chat-widget';
document.body.appendChild(widget); // inconsistent position
}, 5000);Handle conditional help visibility without reordering
If a help mechanism is conditionally shown (e.g., authenticated users see a support ticket link), insert it at a fixed position within the help container rather than toggling it at a different DOM location.
<!-- Consistent order; conditional item stays in place -->
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
<a href="/docs">Documentation</a>
<a href="/support-tickets" class="auth-only hidden">Support tickets</a>
</nav>
</footer><!-- Authenticated: ticket link appended after all footer links -->
<footer class="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
<a href="/docs">Documentation</a>
</nav>
</footer>
<!-- Ticket link appended outside the footer nav, shifting help order -->
<a href="/support-tickets" class="auth-only">Support tickets</a>Verify help order across SPA views
In single-page applications, ensure that shared layout components (headers, footers, sidebar help widgets) containing help mechanisms do not reorder their children when route-specific content is injected.
// Shared footer component renders help links in fixed order
const Footer = () => (
<footer className="site-footer">
<nav aria-label="Help and support">
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
<a href="/docs">Documentation</a>
<a href="/chat">Live chat</a>
</nav>
</footer>
);// Help links reordered per route via conditional rendering
const Footer = ({ route }) => (
<footer className="site-footer">
<nav aria-label="Help and support">
{route === '/checkout' && (
<a href="/chat">Live chat</a> {/* Chat first on checkout */}
)}
<a href="/contact">Contact us</a>
<a href="/faq">FAQ</a>
{route !== '/checkout' && (
<a href="/chat">Live chat</a> {/* Chat last on other pages */}
)}
</nav>
</footer>
);Known Limitations
- Manual-only verification – This rule does not perform any automated DOM comparison across pages. It only reports a reminder to manually verify help order consistency. It cannot detect reordering, and depends entirely on the reviewer’s diligence and judgment.
- Single-page applications (SPAs) – Because SPA content is dynamically swapped without full page reloads, the rule may only evaluate the initial render. Help mechanisms injected after the initial DOM snapshot may not be included in the scan.
- Shadow DOM – Help mechanisms rendered inside shadow trees (e.g., inside Web Components) are not traversed by the selector, which operates on the light DOM only. Help links inside encapsulated components will be missed entirely.
- Dynamically injected third-party widgets – Chat or AI-assistant widgets loaded asynchronously by external scripts (e.g., Intercom, Drift, Zendesk) may not be present when the rule evaluates the page. Their placement cannot be assessed unless they render before the audit snapshot is taken.
- Localized or personalized help mechanisms – If the help links differ in text or href across locales or user roles (e.g., a logged-in user sees “My support tickets” while a guest sees “Contact us”), the rule cannot verify that the relative order among help mechanisms remains the same because it does not compare multiple variants.
- Server-adaptive layouts (adaptive design) – Sites that serve completely different HTML markup based on device detection (user-agent sniffing) rather than responsive CSS may present different DOM structures that the rule cannot cross-reference in a single scan.
Resources
- WCAG 2.2 Success Criterion 3.2.6 Consistent Help – W3C
- Understanding SC 3.2.6 Consistent Help – W3C WAI
- How to Meet WCAG 3.2.6 – W3C WAI Quick Reference
- WCAG Guideline 3.2 Predictable – MDN Web Docs
- Definition: Set of Web Pages – W3C
Rule
- Audit: accessibility
- Standard: WCAG
- Level: A
- Success Criteria: 3.2.6
- Rule ID:
consistent-help