main landmark role is used to indicate the primary content of a document. The main content area consists of content that is directly related to or expands upon the central topic of a document, or the main function of an application.
<div id="main" role="main"> <h1>Avocados</h1> <!-- main section content --> </div>
This is the main section of a document that discusses avocados. Subsections of this document could discuss their history, the different types, regions where they grow, etc.
main role is a navigational landmark role identifying the main content of a document. Landmarks can be used by assistive technology such as screen readers to quickly identify and navigate to large sections of the document.
By classifying and labeling sections of a page, structural information conveyed visually through layout can be represented programmatically. Screen readers use landmark roles to provide keyboard navigation to important sections of a page. For those navigating via landmark roles, the main role is an alternative for "skip to main content" links.
There should only be one
main landmark role per document.
aria-ownsattribute establishes relationships in the accessibility layer that aren't present in the DOM. Documents and applications can be nested in the DOM, which may lead to having more than one main element as DOM descendants. If this is the case, include
aria-ownsto identify the relationship of the main to its document or application ancestor.
Identify the accessible name with
aria-labelledbyif a visible header is present. Otherwise, including an
aria-labelcan be helpful for orienting assistive technology users, especially in single-page applications where main content changes happen without generating a page load event.
<body> <!-- primary navigation --> <div role="main"> <h1>The First Indochina War</h1> <!-- article content --> </div> <!-- sidebar and footer --> </body>
main landmark role should only be used once per document.
If a document contains two
main role's presence should be removed from assistive technology via techniques such as toggling the
<main> <h1>Active `main` element</h1> <!-- content --> </main> <main hidden> <h1>Hidden `main` element</h1> <!-- content --> </main>
It is also helpful to include an accessible name to help orient assistive technology users, especially in single-page applications where main content changes happen without generating a page load event. This can be added with
aria-labelledby if there is an appropriate name in the content, or
aria-label if not.
<main> element will automatically communicate a section has a role of
main. If at all possible, prefer using it instead.
Skip navigation, also known as "skipnav", is a technique that allows an assistive technology user to quickly bypass large sections of repeated content (main navigation, info banners, etc.). This allows the user to access the main content of the page faster.
id attribute to the element with a declaration of
role="main" allows it to be a target of a skip navigation link users.
<body> <a href="#main-content">Skip to main content</a> <!-- navigation and header content --> <div id="main-content" role="main"> <!-- main page content --> </div> </body>
Which is the equivalent of:
<body> <a href="#main-content">Skip to main content</a> <!-- navigation and header content --> <main id="main-content"> <!-- main page content --> </main> </body>
|Accessible Rich Internet Applications (WAI-ARIA) |
|ARIA Authoring Practices |