Only one element may have role=”contentinfo”.
Description
The HTML specification allows only one element to carry the role="contentinfo" landmark on a page. This role identifies the region that typically contains information about the site, such as copyright notices, privacy policies, and contact details – commonly referred to as the footer. When more than one element is assigned this role, assistive technologies cannot reliably identify which element is the canonical site information region, leading to confusion during navigation.
This rule scans the DOM for all elements with role="contentinfo" and reports an issue for every instance when more than one is found. While the native <footer> element implicitly carries this role, explicitly adding role="contentinfo" to multiple elements violates the single-landmark-per-type constraint defined in the WAI-ARIA specification. Use this rule to ensure your page maintains a clear, unambiguous landmark structure.
Disabilities impacted
- Visual impairments – Screen reader users rely on landmarks to jump between page regions. Duplicate
contentinfolandmarks force them to navigate through each one to find the actual footer, wasting time and breaking orientation. - Cognitive disabilities – Users who depend on consistent page structure to understand content get confused when multiple elements claim the same role. A predictable landmark hierarchy reduces cognitive load and supports comprehension.
- Motor disabilities – Keyboard-only users navigate by landmarks to minimize keystrokes. Two or more
contentinforegions increase the number of stops in the landmark list, requiring extra key presses and reducing efficiency. - Deaf-blind users – Those using refreshable Braille displays paired with screen readers depend on accurate landmark labels. Duplicate landmarks produce identical labels on the Braille display, making it impossible to distinguish the true footer from a spurious one.
Why it matters
The WAI-ARIA Authoring Practices specify that each landmark type should appear at most once unless there is a clear, labeled distinction. When multiple elements share role="contentinfo", assistive technology presents them with identical roles, giving users no way to differentiate between a real footer and another element that was mistakenly given the same role.
This ambiguity degrades navigation efficiency for all assistive technology users. It also signals a structural problem in the markup that can affect automated accessibility auditing, SEO crawlers that parse semantic regions, and maintainability of the codebase.
Coding problems and solutions
Common coding problems
- Multiple footer elements – Using more than one
<footer>on the same page without distinguishing them viaaria-label, resulting in multiple implicitcontentinfolandmarks. - Redundant role attribute – Adding
role="contentinfo"to a<footer>element that already carries the role implicitly. - Component library duplication – A layout component that renders a sticky footer and a page-level footer, both with
role="contentinfo". - SPA template inheritance – A global footer component is included in both the layout shell and a nested page template, producing two instances in the DOM.
- Template partial misuse – A footer partial is included via server-side include or template engine in two different containers that are both visible at the same time.
How to fix it
Use the native <footer> element once
The simplest approach is to use a single <footer> element at the page level. The element implicitly carries the contentinfo role, so no explicit role attribute is needed.
<body>
<main>
<h1>Article Title</h1>
<p>Page content goes here.</p>
</main>
<footer>
<p>© 2026 My Company. All rights reserved.</p>
</footer>
</body><body>
<main>
<h1>Article Title</h1>
<p>Page content goes here.</p>
</main>
<footer role="contentinfo">
<p>© 2026 My Company. All rights reserved.</p>
</footer>
<div role="contentinfo">
<p>Additional site information.</p>
</div>
</body>Use aria-label to distinguish multiple footer-like regions
If you genuinely need more than one footer-like region, assign distinct aria-label values so assistive technologies can differentiate them. Only one should carry role="contentinfo"; use a different role for the other.
<footer aria-label="Site footer">
<p>© 2026 My Company.</p>
</footer>
<aside aria-label="Related links">
<nav aria-label="Related">
<ul>
<li><a href="/terms">Terms of Service</a></li>
<li><a href="/privacy">Privacy Policy</a></li>
</ul>
</nav>
</aside><footer role="contentinfo">
<p>© 2026 My Company.</p>
</footer>
<div role="contentinfo">
<nav>
<ul>
<li><a href="/terms">Terms</a></li>
<li><a href="/privacy">Privacy</a></li>
</ul>
</nav>
</div>Remove the redundant role="contentinfo" from native footers
When using the <footer> element, the role is applied automatically. Adding it explicitly is redundant and, if done on multiple footers, produces duplicate landmarks.
<footer>
<p>Contact us at info@example.com</p>
</footer><footer role="contentinfo">
<p>Contact us at info@example.com</p>
</footer>Deduplicate footer components in SPA frameworks
In single-page applications, ensure the footer component is rendered exactly once at the layout level and not also inside individual page components.
// Layout component renders the footer once
const Layout = ({ children }) => {
return (
<div>
<header role="banner">...</header>
<main role="main">{children}</main>
<footer>
<p>© 2026 My Company</p>
</footer>
</div>
);
};// Page component duplicates the footer
const HomePage = () => {
return (
<div>
<h1>Welcome</h1>
<p>Home page content.</p>
<footer>
<p>© 2026 My Company</p>
</footer>
</div>
);
};
// Layout also includes the footer
const Layout = ({ children }) => (
<div>
{children}
<footer>
<p>© 2026 My Company</p>
</footer>
</div>
);Guard against duplicate includes in template engines
When using server-side templates, ensure footer partials are included only within a single parent container that is visible at any given time.
<!-- main-layout.html -->
<html>
<body>
{% include "header.html" %}
<main>{% block content %}{% endblock %}</main>
{% include "footer.html" %}
</body>
</html><!-- main-layout.html -->
<html>
<body>
{% include "header.html" %}
<main>{% block content %}{% endblock %}</main>
{% include "footer.html" %}
</body>
</html>
<!-- page.html (extends layout) -->
{% extends "main-layout.html" %}
{% block content %}
<p>Page content.</p>
{% include "footer.html" %}
{% endblock %}Known Limitations
- Shadow DOM – Elements inside a shadow root with
role="contentinfo"may not be visible to selectors that operate on the light DOM. The rule’s selector[role="contentinfo"]does not penetrate shadow boundaries by default, so duplicates inside shadow roots may go undetected. - Iframes – Content loaded within
<iframe>elements exists in a separate document context. Anycontentinfolandmarks inside iframes are not part of the parent page’s accessibility tree and will not be counted by this rule. - Dynamic SPA rendering – In frameworks that mount and unmount components asynchronously, the number of
contentinfolandmarks may change over the page lifecycle. This rule captures a single DOM snapshot and may miss transient duplicates or those that appear only after user interaction. - CSS-hidden duplicates – Elements with
role="contentinfo"that are visually hidden viadisplay: noneorvisibility: hiddenare still present in the DOM and will be reported, even though they are not perceivable to sighted users. This is technically correct per the spec but may produce false positives in some workflows. - Incorrect ARIA usage elsewhere – The rule only checks for duplicate
contentinforoles. It does not verify whether the element is semantically appropriate to carry the role (e.g., a<div role="contentinfo">inside an article may be semantically incorrect even if it is the only one on the page).
Resources
- WAI-ARIA 1.2 – contentinfo Role
- WAI-ARIA Authoring Practices – Landmarks
- MDN – contentinfo Role
- WCAG 2.2 – 1.3.1 Info and Relationships
Rule
- Audit: accessibility
- Standard: SiteLint
- Level: Best practices
- Success Criteria: N/A
- Rule ID:
contentinfo-landmark-only-one