The contentinfo role defines a footer, containing identifying information such as copyright information, navigation links, and privacy statements, found on every document within a site. This section is commonly called a footer.
<div role="contentinfo">
<h2>Footer</h2>
</div>
This is a website footer. Using the footer element instead is recommended:
<footer>
<h2>Footer</h2>
</footer>
Description
The contentinfo role is a landmark used to identify a page footer. Landmarks can be used by assistive technology to quickly identify and navigate to large sections of the document. Pages should only include one top-level contentinfo landmark role per page.
Each page should only include one contentinfo landmark, created by either using the footer element or by declaring role="contentinfo". contentinfo landmarks present in content embedded via iframe do not count towards this limit.
[!NOTE] Using the footer element will automatically communicate a section has a role of
contentinfo. Developers should always prefer using the correct semantic HTML element over using ARIA, making sure to footer#accessibility in VoiceOver.
Examples
<body>
<div role="contentinfo">
<h2>MDN Web Docs</h2>
<ul>
<li><a href="#">Web Technologies</a></li>
<li><a href="#">Learn Web Development</a></li>
<li><a href="#">About MDN</a></li>
<li><a href="#">Feedback</a></li>
</ul>
<p>
© 2005-2012 Mozilla and individual contributors. Content is available
under <a href="#">these licenses</a>.
</p>
</div>
</body>
Accessibility concerns
Use sparingly
Landmark roles are intended to identify larger overall sections of the document. Using too many landmark roles can create "noise" in screen readers, making it difficult to understand the overall layout of the page.
One contentinfo landmark per page
The <body> element
There should be only one contentinfo landmark per document, used as the immediate descendant of the body element.
Mega-footers
Do not nest additional footer elements or contentinfo landmarks inside the document's footer. Use other content sectioning elements instead.
Labeling landmarks
Multiple landmarks
If there is more than one contentinfo landmark role or footer element in a document, provide a label with the aria-label attribute for each landmark. This label will allow assistive technology users to quickly understand the purpose of each landmark.
<body>
…
<article>
<h2>Everyday Pad Thai</h2>
<footer aria-label="Everyday Pad Thai metadata">
<p>
Posted on <time datetime="2021-09-23 12:17">September 23</time> by
<a href="#">Lisa</a>.
</p>
</footer>
</article>
…
<footer aria-label="Footer">
</footer>
</body>
Redundant descriptions
Screen readers will announce the type of role the landmark is. Because of this, you do not need to describe what the landmark is in its label. For example, a declaration of role="contentinfo" with an aria-label="Footer" may be announced redundantly as, "contentinfo footer".
Best practices
Prefer HTML
When it is an immediate descendant of the body using the footer element will automatically communicate a section has a role of contentinfo (save for footer#accessibility in VoiceOver). If at all possible, prefer using <footer> instead. Note that a footer element nested within an article, aside, main, nav, or section is not considered contentinfo.
Added benefits
Certain technologies such as browser extensions can generate lists of all landmark roles present on a page, allowing non-screen reader users to also quickly identify and navigate to large sections of the document.
Specifications
See also
- The footer element
- Using HTML sections and outlines
- Accessible Landmarks | scottohara.me
- The Footer Element Update | HTML5 Doctor
来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。
