landmark
A region of a page, such as navigation, main content or footer, that assistive technology users can jump between.
In more detail
Landmarks come from elements such as <nav>, <main>, <header> and <footer>, or from ARIA roles. Site navigation belongs in a <nav> landmark with an ordinary list of links rather than an ARIA menu.
Example
In the browser: Elements like header, nav, main, aside and footer map to landmark roles automatically. Screen reader users can list the landmarks and skip straight to the main content instead of hearing the whole page.Related terms
- semantic HTML — Using HTML elements for their meaning, such as <button> for actions and <nav> for navigation, rather than generic <div>s.
- menu role — The ARIA role for an application-style list of actions, like a File or Edit menu, navigated with arrow keys.
- main element — The HTML element that wraps the dominant, unique content of a page, used once per page and exposed as the main landmark.
- nav element — The HTML element for a block of major navigation links, exposed as a navigation landmark.
- screen reader — Software that reads the screen aloud or sends it to a braille display, used mainly by blind and low-vision people.
- ARIA role — The role attribute that tells assistive technology what kind of thing an element is, such as button, dialog, tab or switch.
Taught in
- Navigation & Disclosure: Dropdown Menus, Tabs & Accordions — Design Systems & Component Engineering
- Automated Accessibility Testing: axe-core & Testing Library — Design Systems & Component Engineering
- Semantic HTML Elements: Landmarks And Structure — Frontend Architecture & Web Platform
- Accessibility Tree, ARIA Roles, States And Live Regions — Frontend Architecture & Web Platform