WCAG 2.4.8: Location

Quick answer: Users should be able to determine their location within site hierarchy, flows, or account sections.

What This Means

On ecommerce sites, Location 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 collection subcategories open with no breadcrumb trail. or help-center articles lack a visible path back to the section., 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

• Collection subcategories open with no breadcrumb trail.
• Help-center articles lack a visible path back to the section.
• Account pages do not indicate which area—orders, addresses, or subscriptions—is active.
• Multi-step checkout shows the current step only by color.

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.

1. Add breadcrumbs, step indicators, and active navigation states.
2. Expose current location with text, not color alone.
3. Keep hierarchical navigation visible on mobile where possible.
4. Mark the current page or step programmatically using aria-current when appropriate.

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 -->
<nav><a href="/account/orders">Orders</a></nav>

<!-- After -->
<nav aria-label="Breadcrumb"><a href="/collections">Collections</a> / <span aria-current="page">New arrivals</span></nav>

Check if your store passes WCAG 2.4.8 → Free ADA Compliance Scan