Contentinfo landmark should not be contained in another landmark

WCAG 1.3.1
Info and Relationships

Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).

Why this matters and how to fix it

Why this matters

The contentinfo (typically <footer>) represents site-level information. If it’s nested, screen readers may announce it in the wrong context.

How to fix this issue

Ensure <footer> or role='contentinfo' is a direct child of <body> and not nested within <main> or <article>.

Automated detection · Manual review recommended

Developer guidance

Use only one top-level <footer>. Section-specific footers may exist, but they should not have role='contentinfo'.

Code examples

Incorrect Implementation

<main>
  <footer role='contentinfo'>© 2025 MySite</footer>
</main>

Correct Implementation

<footer role='contentinfo'>© 2025 MySite</footer>
<main>
  <article>Page content</article>
</main>
eu icon getwcag

Trusted by organizations across Europe working toward WCAG and EAA conformance