A11y 101 – 3.2.3 Consistent Navigation

Imagine walking into your favorite library. You know exactly where the fiction section is. It’s always on the second floor, to the left of the stairs. The librarian knows where you go. Your feet know the way. It’s muscle memory.

It is a week later when you walk in, and suddenly fiction is in the basement, behind the coffee shop, accessible only through a secret door behind the periodicals. The stairs are now an elevator, but it’s on the other side of the building. The librarian has vanished.

You’d feel disoriented. Frustrated. Maybe even a little unsafe. You’re just trying to find a book, not solve a puzzle.

The Clash released a song, “Lost in a supermarket.” I know I often feel this way. The outer ring of the store stays the same with produce, deli, bakery, meat cases, and dairy. But the bread has moved to where the soda was. Snacks are now in the International aisle, which hasn’t been renamed yet. Your normal 45 minute trip to the grocer’s just took twice as long.

That’s what happens to users when navigation jumps around from page to page. And that’s exactly what WCAG 3.2.3: Consistent Navigation is here to stop.

Keep the Path Clear

Identifying components that have the same functionality across multiple pages must be presented consistently.

If your “Home,” “About,” and “Contact” links are in the top right corner on the homepage, they should be in the top right corner on every single page they appear on. If your search bar is at the bottom, I wonder about your user experience research, but leave it there. If the main menu opens by clicking a hamburger icon, don’t switch to a side drawer on the next page.

It doesn’t mean the content has to be identical. It means the mechanism to get around stays the same within a set of pages. If you have an application, within the application (a set) the navigation needs the consistency. But if you go to the documentation for that application, this set can have a different navigation as long as it is consistent within the set.

Cognitive Load is Real

For many users, especially those with cognitive disabilities, memory issues, or learning differences, re-learning a layout on every new page is exhausting. Every time the navigation moves, the brain has to stop scanning for the goal and start scanning for the controls. That mental friction adds up fast.

Screen reader users rely on predictable patterns too. They often navigate by landmark regions (<nav>, <main>) and heading structures. If the order of these landmarks changes unpredictably, their mental map of the site collapses. They might miss a critical link because they assumed it was in its usual spot, or they might tab through five irrelevant items before finding the one they need.

When navigation is consistent, users can focus on content, not controls.

The Exceptions (Yes, There Are Some)

There are a few places where consistency doesn’t apply, and it’s important to know them so you don’t over-engineer your solution:

• Sub-navigation: If you have a secondary menu specific to a section (like a list of blog categories within the Blog page), that doesn’t need to match the main global nav.
• Process-specific steps: In a checkout flow or a multi-step wizard, the navigation might change to reflect the process (e.g., “Back,” “Next,” “Review”). That’s context-appropriate.
• Page-specific functions: If a page has unique features (like a dashboard with filters), those don’t need to exist elsewhere.

But the core navigation—the stuff that takes you between major sections? That needs to stay put.

Consistency is a form of empathy.

When we design interfaces where navigation drifts, we’re essentially saying, “We assume you can handle constant change. We assume you won’t get lost.”

But we know better. We know that the web can be overwhelming. We know that anxiety spikes when things aren’t where they should be. By locking down the navigation, we’re giving users a safe harbor. We’re saying, “You know where the door is. You know how to get back home. Rest easy.”

That’s not just good UX. It’s good humanity.

3.2.3 isn’t about restricting creativity. It’s about respecting the user’s journey.

Don’t reinvent the wheel on every page. Don’t move the furniture while they’re sitting in it. Keep the path clear, keep the signs the same, and let them focus on what matters: the content.

Your users will thank you for the familiarity. And in a world full of chaos, familiarity is a superpower.

Want to talk about this more? Find me over on LinkedIn and Bluesky!