A landmark identifies a major area of a page so people can move to it without exploring every element first. Screen reader users can choose from a list of landmarks; keyboard users may use them as skip-link targets; voice-control users can ask to go to an area such as main content. Clear landmarks make a page easier to explore and stay oriented in. section 5.2
Start with semantic HTML. Use <header>, <nav>, one <main>, and <footer> for the corresponding page areas. These elements communicate their purpose programmatically without an added ARIA role. Use an ARIA landmark role on a generic container only when a native element cannot be used, such as in a constrained legacy system. section 2.5.1 section 5.2
Make repeated navigation areas distinguishable
A page with both primary and footer navigation should not leave users guessing which navigation landmark they have reached. Give each <nav> a distinct accessible name, such as <nav aria-label="Primary"> and <nav aria-label="Footer">. section 2.5.1 section 5.2
TIP: A skip link can point to the main region: <a href="#main">Skip to main content</a> can reference <main id="main">. This gives users a way past repeated navigation links. section 5.2 section 5.6
<section aria-labelledby="section-title"> #A <h2 id="section-title">...</h2> ... </section>
A section becomes a named region when aria-labelledby points to its heading. Use this pattern when the section is important enough to be a direct navigation destination. section 5.2 section 2.5.1
NOTE: More landmarks are not always better. Naming every section can clutter a screen reader’s list of destinations. A heading is often enough: use <section> for a distinct part of the page and <div> for generic grouping. Ask whether someone would benefit from jumping directly to the region. section 2.5.1
