Users jump by heading, landmark, and element type
Aliases: reader jumps · landmark navigation · rotor
What it is
Nobody listens from the first header link down to the footer. Screen-reader users jump by heading, landmark, and element type (button, link, form control), turning a long sequence into a table of contents. That practice is screen reader navigation. It is not reading the page as an article.
Why it happens
Hearing a whole page linearly grows with object count; the task cannot wait. Readers therefore filter by type: a heading list is a chapter index, a landmark list is “navigation / main / search / footer,” a type list is “every button on this page.” The question shifts from “what is the next sentence” to “which item in which class.”
The jump vocabulary is types, not visual regions. “The column on the right” is not a command; “the third heading” or “main” is. If those types are not exposed, jump commands return empty lists and the user is forced back to item-by-item listening. Whether the hooks exist decides whether the movement strategy can work, not whether the page looks tidy.
Studying it
Same task, three strategies: listen from the top, jump by headings only, jump by landmarks only. Record which command first lands on the target control.
Independent variables: completeness of headings / landmarks / types, page length, user experience. Dependent variables: jump count, fallbacks to linear browsing, time to target.
On desktop, heading shortcut keys; on mobile, the rotor set to Headings, then swipe. Test both — the commands differ, an empty list fails the same way.
Where it stops holding
In a short dialog the payoff is small: a few Tabs or swipes suffice. If every card is a heading and landmarks pile into a dozen, the index itself becomes noise and jumps lose value. Keyboard-only tests miss rotor users; VoiceOver-only tests miss NVDA’s element lists. Hooks can be complete and the user still go wrong because order is scrambled — that is a different failure.
Applying it
- Give every major region a jumpable hook: one top-level heading for the page topic, headings for sections, landmarks for navigation / main / footer.
- Make buttons, links, and form controls real types so they appear in type lists.
- How to check: open the reader’s heading list and landmark list. The entry to the target task should be nameable in those lists. An empty list, or a list of “click here,” means the jumps have no material.