Table Navigation and Testing
You'll learn how to use screen reader table navigation commands to verify that data tables announce their structure and cell relationships correctly.
Understanding Table Navigation in Screen Readers
When a screen reader user encounters a data table (like a schedule or pricing comparison), they don't see it visually laid out. Instead, they navigate cell-by-cell, relying on the screen reader to announce where they are: "Row 2, Column 3, Sales, January."
Screen readers provide special table navigation commands that let users move through tables efficiently—jumping between rows, columns, or headers—but this only works when the HTML is properly structured with <table>, <th>, <tr>, and <td> elements.
Key Table Navigation Commands
Both NVDA and VoiceOver provide table-specific shortcuts:
- Navigate to next/previous table: Jump between tables on a page
- Move by row: Ctrl+Alt+Arrow keys (NVDA) or VO+Arrow keys (VoiceOver)
- Move by column: Similar arrow key combinations
- Read current cell: Screen reader announces the cell content plus associated headers
- Read column header: Hear which column you're in
- Read row header: Hear which row you're in
What to Test
When testing a data table, verify that:
- The screen reader announces you're entering a table and states its dimensions ("Table with 5 rows and 4 columns")
- Column headers (
<th scope="col">) are announced when navigating cells - Row headers (
<th scope="row">) are announced for each data cell - Complex tables with
headersattributes correctly associate cells with multiple headers - Table captions (
<caption>) provide context about the table's purpose
Key Takeaway: Screen reader table navigation relies entirely on semantic HTML structure—test by navigating cell-by-cell and ensuring headers are properly announced with each data cell, giving users the context they need to understand the information.