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

Heading Navigation and Structure Testing

Using screen reader heading lists to verify proper document outline and hierarchy.

Heading Navigation and Structure Testing

You'll learn how to use a screen reader's heading list feature to quickly verify that your page has a logical, well-organized structure.

Why Headings Matter for Screen Reader Users

Screen reader users often navigate by headings rather than reading every word. Think of it like scanning a table of contents in a book—you jump to the chapter you need instead of reading cover to cover. Screen readers provide a dedicated "heading list" feature that shows all headings (<h1> through <h6>) in order, letting users jump directly to any section.

How to Access the Heading List

In NVDA (Windows): Press Insert + F7 to open the Elements List, then select the "Headings" tab. You'll see all headings in document order.

In VoiceOver (macOS): Open the rotor with Control + Option + U, then use left/right arrows to navigate to the "Headings" menu. All headings appear as a navigable list.

What to Test

When reviewing the heading list, check:

  1. One <h1> per page — The main title of the content
  2. No skipped levels — Don't jump from <h2> to <h5>
  3. Logical hierarchy — Subsections use higher heading numbers
  4. Descriptive text — "Contact Information" not just "Info"
  5. Document outline makes sense — Could someone understand the page structure from headings alone?

For example, a blog post might show:

  • H1: "Understanding Web Accessibility"
  • H2: "Why It Matters"
  • H2: "Common Mistakes"
  • H3: "Missing Alt Text"
  • H3: "Poor Color Contrast"

Key Takeaway: Use your screen reader's heading navigation feature to verify your page has a clear, hierarchical outline—if the heading list tells a coherent story, your structure is solid.