Goal
Help users understand where they are within a site.
Success Criterion · WCAG 2.4.8
Location
Information about the user's location within a set of Web pages is available.
Level AAAWCAG 2.0Operable2.4 · Navigable
Copy button ready
What to do
Provide information about the user’s current location within a set of pages (e.g., breadcrumbs, highlighted navigation, or “You are here”).
Why it matters
Orientation cues reduce confusion and improve navigation for users with cognitive disabilities and screen reader users.
Success criterion
What WCAG 2.4.8 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Information about the user’s location within a set of Web pages is available.
Intent
Why WCAG created this requirement
- Users need context within site structure to navigate effectively.
- Breadcrumbs and navigation indicators provide orientation.
- This is especially helpful for large sites and deep hierarchies.
Benefits
Who gains when you pass
- Users with cognitive disabilities can understand their context and backtrack.
- Screen reader users can identify location without guessing from page content alone.
- All users benefit from clearer navigation and wayfinding.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users can get lost in deep navigation structures.
Users may repeatedly backtrack or abandon when they don’t know where they are.
Overview
Users should be able to determine their location within the site or app structure. Common solutions include breadcrumbs, a page “current” indicator in navigation, or a clear “You are here” cue.
- Use breadcrumbs with accessible markup (`nav` + `aria-label`, ordered list).
- Mark current nav item with `aria-current="page"`.
- Ensure location cues are consistent across pages.
Reference: All summaries and highlights originate from Understanding WCAG 2.4.8 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.4 · Navigable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Breadcrumbs
Pass
Breadcrumbs: Home → Tools → Contrast Checker, with current page not linked.
Fail
No breadcrumb or current location indication on deep pages.
Current nav item
Pass
Sidebar highlights the current page and uses `aria-current="page"`.
Fail
Nav has no indication of which page is active.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document breadcrumb structure and rules for when to show it.
- Maintain a navigation map and confirm location cues match it.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Add breadcrumbs for hierarchical sections where appropriate.
- Ensure primary navigation indicates the current page (aria-current + visual style).
- Provide consistent page titles/headings that reflect the navigation location.
- Ensure breadcrumbs and nav are keyboard accessible and announced correctly.
Testing ideas
Prove conformance with evidence
- Navigate to multiple pages and verify location cues are present.
- Use a screen reader to ensure breadcrumbs/nav current page is announced.
- Verify `aria-current` is used appropriately and only on the current page item.
Related success criteria
More from Navigable (2.4)
WCAG 2.4.1Bypass BlocksLevel AWCAG 2.4.2Page TitledLevel AWCAG 2.4.3Focus OrderLevel AWCAG 2.4.4Link Purpose (In Context)Level AWCAG 2.4.5Multiple WaysLevel AAWCAG 2.4.6Headings and LabelsLevel AAWCAG 2.4.7Focus VisibleLevel AAWCAG 2.4.9Link Purpose (Link Only)Level AAAWCAG 2.4.10Section HeadingsLevel AAAWCAG 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.4.12Focus Not Obscured (Enhanced)Level AAAWCAG 2.4.13Focus AppearanceLevel AAA