Course contentsShow
← Web Development
Lesson 1105 of 2,98220. Screen Readers and Assistive TechnologyFree lesson

Landmark and Region Navigation

Testing landmark navigation to ensure proper page structure and skip functionality.

Landmark and Region Navigation

What you'll learn: How to verify that screen readers can jump between major page sections using landmark navigation commands.

What Are Landmarks in Screen Reader Testing?

When you defined semantic regions like <header>, <nav>, <main>, and ARIA landmark roles earlier, you created "jumping points" for screen reader users. Now you need to test that these work correctly—that users can actually hop from section to section without listening to every word in between.

Think of landmarks like chapters in an audiobook. Instead of listening start-to-finish, you can skip to "Chapter 3: Main Content" or "Chapter 7: Footer." Screen readers offer special commands to browse these regions quickly.

Testing Landmark Navigation

In NVDA (Windows):

  • Press D to jump to the next landmark
  • Press Shift + D to go backwards
  • Press Insert + F7 to see a list of all landmarks

In VoiceOver (macOS):

  • Open the rotor with VO + U, then arrow to "Landmarks"
  • Navigate with arrow keys
  • Press Enter to jump to a selection

What You're Testing For

As you navigate, confirm:

  • Each major page section appears as a distinct landmark
  • Labels are announced clearly (e.g., "navigation: Main menu" vs just "navigation")
  • You can reach all important page areas without tabbing through everything
  • Users aren't trapped or forced to use heading navigation exclusively

If you have multiple <nav> elements but haven't labeled them with aria-label, you'll hear "navigation... navigation... navigation" with no way to distinguish them—a clear failure.

Key Takeaway: Testing landmark navigation ensures users can efficiently explore your page structure by jumping between major sections, not just headings or links.