WCAG 3.2.6: Consistent Help
Level AQuick answer: If help is repeated across pages, it should appear in a consistent place so users can find support quickly.
What This Means
On ecommerce sites, Consistent Help usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like chat support is bottom right on pdps but hidden in a top banner on checkout. or returns help moves between footer, sidebar, and modal depending on template., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Chat support is bottom right on PDPs but hidden in a top banner on checkout.
- Returns help moves between footer, sidebar, and modal depending on template.
- Phone and email support links change order across account pages.
- A help icon exists on product pages but disappears on payment pages where users need it most.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Keep repeated support entry points in a stable location across templates.
- Use the same label and icon pattern for contact methods sitewide.
- Do not bury help deeper on high-friction pages like checkout and account recovery.
- Document help-placement rules for design and merchandising teams.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<aside class="help-top">Need help?</aside>
<!-- After -->
<aside class="help-rail">Need help? Chat, email, or call us.</aside>FAQ
What is WCAG 3.2.6?
If help is repeated across pages, it should appear in a consistent place so users can find support quickly.
How does WCAG 3.2.6 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with chat support is bottom right on pdps but hidden in a top banner on checkout. and returns help moves between footer, sidebar, and modal depending on template. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.2.6 violations?
Start by auditing the live storefront, then Keep repeated support entry points in a stable location across templates.; Use the same label and icon pattern for contact methods sitewide.; Do not bury help deeper on high-friction pages like checkout and account recovery.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.2.6 → Free ADA Compliance Scan