---
id: kb_navigation_wayfinding_page_structure
title: Wayfinding and page structure
category: navigation
appliesToAppTypes: [generic]
appliesToLenses: [usability, accessibility]
steps: [evaluate]
tags: [navigation, wayfinding, landmarks, structure]
citation:
  source: "W3C WAI: Page Regions"
  url: "https://www.w3.org/WAI/tutorials/page-structure/regions/"
  retrievedAt: "2026-06-01T00:00:00.000Z"
freshness:
  volatility: stable
  lastReviewed: "2026-06-01T00:00:00.000Z"
---

## Summary

Pages should expose clear structure, current location, and predictable navigation paths so users
can orient and move without rereading the whole interface.

## Deep Guidance

Look for a named main region, clear headings, discoverable navigation landmarks, current-page
state, and labels that describe destinations rather than implementation details. Flag navigation
when users cannot tell where they are, what section they are in, which route is active, or where
a primary path will take them. Prefer fixes that preserve familiar web conventions: semantic
regions, stable placement, concise destination labels, active-state cues, and breadcrumbs or
section headers when hierarchy matters.