liveBook · Manning

ARIA landmark role

As explained in Architecting Accessibility

An ARIA landmark role is an ARIA semantic role that exposes an interface region as a navigable landmark.

Landmarks give screen reader, keyboard, and voice-control users navigable beacons for finding page regions. section 5.2

Prefer semantic HTML such as <header>, <main>, <nav>, and <footer>, which expose landmarks automatically. Use ARIA landmark roles to reproduce those semantics only when native elements cannot be used, such as in legacy layouts built around generic <div>s. section 5.2

Label distinct navigation landmarks

Give separate navigation areas distinct names, such as “Primary” and “Secondary,” so users can tell them apart. section 5.2

Table 5.1 Native HTML elements and their corresponding ARIA landmark roles and purposes.
HTML
Landmark role
Notes
<aside>
complementary
Content that is partially related to the surrounding content, such as adverts, highlights, or related links.
<footer>
contentinfo
A footer contains meta-information about a page, such as copyright information. There should typically be one contentinfo landmark per page. A <footer> element is only exposed as a contentinfo landmark when it is not a descendant of elements such as <article>, <aside>, <main>, <nav>, and <section>.
<form>
form
A form is a collection of input fields and related controls. Both <form> and elements with role="form" are only exposed as landmarks when they have an accessible name using aria-label, aria-labelledby, or title). It is not recommended to use the title attribute, as it is not consistently supported by assistive technologies.
<header>
banner
The <header> element represents introductory content and can be used at the page or section level (such as in <article>). It is exposed as a banner landmark only when it is not a descendant of elements such as <article>, <aside>, <main>, <nav>, and <section>.
<main>
main
Represents the primary content of the document. There should only be one per page
<nav>
navigation
Represents a section of navigation links. If multiple navigation landmarks exist, they should be uniquely labeled using aria-label or aria-labelledby.
<section>
region
Represents grouped content related to a document (such as pricing details or related products). A <section> is only exposed as a region landmark when it has an accessible name, provided using aria-labelledby (typically referencing the id of a visible heading ( <h1>- <h6>) within the section), aria-label, or title (not recommended – see <form>).
<search>
search
Represents search or filtering functionality. <search> maps to role="search". If multiple search landmarks exist, they should be uniquely labeled using aria-label or aria-labelledby.
<article>
Not applicable
This is used for self-contained content in a document that can be distributed independently, such as a newspaper article, blog entry, or comment. It does not have a corresponding ARIA role, but is still an HTML sectioning element.

Compare native HTML elements with their corresponding landmark roles and notes on when elements qualify. section 5.2

How Architecting Accessibility covers it

How deep it goes
Explains native-to-role mappings and navigation benefits, but does not detail role implementations.
Examples
Uses native landmark elements and distinctly named primary and secondary navigation areas.
What you can do after
Evaluate/understand when to use ARIA landmark roles instead of native semantic HTML.
How it connects
Connects landmarks with semantic HTML, screen readers, keyboard navigation, voice control, and skip links.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.