WCAG 2.4.8 Location: Show Users Where They Are in Your Site

Last updated: 2026-04-17

Level AAA Operable WCAG 2.4.8

What This Criterion Requires

WCAG 2.4.8 Location is a Level AAA success criterion that requires information about the user's location within a set of pages to be available. In practice this means that on any given page the user can quickly answer the question "Where am I?" without relying on the URL bar. Common implementations include breadcrumb trails that show the path from the home page, a current-page indicator in the primary navigation, a sitemap that highlights the active section, or a step counter such as "Step 3 of 5" inside a multi-page form. The criterion is especially important for sites with deep hierarchies (documentation, government services, large e-commerce catalogs) and for users who arrive deep in the site through search results. Although it sits at Level AAA, breadcrumbs and active-state styling are inexpensive to implement and frequently overlap with SEO best practices, so many design systems satisfy it by default.

Why It Matters

Users with cognitive disabilities, attention difficulties, or memory impairments are disproportionately disoriented when they cannot tell where a page sits within a larger structure. A clear location indicator shortens the cognitive distance between landing on a page and deciding what to do next. The criterion also benefits users who navigate by keyboard or screen reader and cannot quickly scan a complex visual hierarchy, users on small mobile screens where global navigation collapses behind a menu icon, and users following a multi-step task who need to know how much further they have to go. From a business perspective, breadcrumb-style location cues reduce bounce rates from search-engine traffic, because visitors who land on a deep page can climb back to a relevant category instead of leaving. Sites with deep information architectures that fail this criterion typically see higher abandonment in funnels and more support requests asking "how do I get back to ___?".

Common Failures and How to Fix Them

No breadcrumbs and no active-state in primary navigation

A deeply nested article page has no breadcrumb trail, and the primary navigation does not visually mark the section the user is currently in. The only location cue is the URL.

Inaccessible 
<nav aria-label="Primary">
  <a href="/products">Products</a>
  <a href="/support">Support</a>
  <a href="/blog">Blog</a>
</nav>
<!-- No breadcrumb, no aria-current -->
Accessible 
<nav aria-label="Primary">
  <a href="/products">Products</a>
  <a href="/support" aria-current="page">Support</a>
  <a href="/blog">Blog</a>
</nav>
<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Home</a></li>
    <li><a href="/support">Support</a></li>
    <li><a href="/support/billing">Billing</a></li>
    <li aria-current="page">Refund policy</li>
  </ol>
</nav>

Multi-step form with no step counter

A checkout or application form spans multiple pages, but no page tells the user which step they are on or how many remain. Users cannot estimate effort or locate themselves in the flow.

Inaccessible 
<h1>Shipping address</h1>
<form>
  <!-- fields -->
</form>
<!-- No indication that this is step 2 of 4 -->
Accessible 
<nav aria-label="Checkout progress">
  <ol class="steps">
    <li>Cart</li>
    <li aria-current="step">Shipping address (step 2 of 4)</li>
    <li>Payment</li>
    <li>Review</li>
  </ol>
</nav>
<h1>Shipping address</h1>
<form><!-- fields --></form>

Breadcrumbs implemented as plain text without semantic structure

A breadcrumb-like string appears in the page header but is not marked up as a list or as a navigation landmark, so assistive technology cannot expose it as a location cue.

Inaccessible 
<div class="crumbs">Home &gt; Docs &gt; API &gt; Webhooks</div>
Accessible 
<nav aria-label="Breadcrumb">
  <ol class="crumbs">
    <li><a href="/">Home</a></li>
    <li><a href="/docs">Docs</a></li>
    <li><a href="/docs/api">API</a></li>
    <li aria-current="page">Webhooks</li>
  </ol>
</nav>

How to Test

  1. Land on a deep page through a search engine result and confirm that within 5 seconds a sighted user can identify which section of the site the page belongs to, without reading the URL.
  2. Navigate the page with a screen reader and verify that either a breadcrumb landmark, an aria-current indicator in the primary navigation, or a labelled step counter is announced as part of the page orientation.
  3. Inspect breadcrumb trails to confirm they are wrapped in a nav element with an accessible name (aria-label or aria-labelledby) and that the final crumb uses aria-current="page" instead of being a link.
  4. For multi-step processes, walk through each step and verify that every page exposes the current step number and total number of steps, both visually and to assistive technology.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

Further Reading

Related WCAG Criteria