Navegação por marcos: como os usuários se deslocam

A sighted user glances around a page. A screen reader user instead jumps region to region using landmarks you defined.

Most screen readers offer a key to cycle landmarks. In NVDA the D key hops to the next region without touching the mouse.

Users can also open a landmarks list, a menu of every region on the page, and pick one to leap straight there.

The big win is skipping. Users jump past the header and nav they have heard before, landing right on fresh content.

On a Mac, VoiceOver users open the rotor and choose Landmarks to navigate your regions by name and role.

In that landmark list, your aria-label values become the menu items, so good names are what make jumping useful.

Landmarks are visited in source order, so a logical HTML order means a logical jump order for everyone.

If every box is a region, the list becomes noise. Use landmarks for true page sections, not for general layout.

Ideally all visible content sits inside some landmark. Orphan content outside any region is harder to reach by jumping.

Open a screen reader and press the landmark key. If you can jump cleanly through your page, your regions are working. 🎧

Landmark jumps beat pressing Tab dozens of times. A few keystrokes replace a long, tiring crawl through every link.

What is the main benefit of landmark navigation for screen reader users?

You learned how users hop between landmarks with a key or rotor, why named regions and DOM order matter, and to test by ear. 🙌