Document should not have more than one contentinfo 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

Screen reader users expect one contentinfo landmark (footer). Multiple confuse navigation and document structure.

How to fix this issue

Use one <footer> element or one role='contentinfo' per document. Convert other footers to generic <footer> without role='contentinfo'.

Automated detection · Manual review recommended

Developer guidance

The contentinfo landmark must contain site-level info like copyright or contact links.

Code examples

Incorrect Implementation

<footer role='contentinfo'>© 2025 MySite</footer>
<article>
  <footer role='contentinfo'>Related links</footer>
</article>

Correct Implementation

<footer role='contentinfo'>© 2025 MySite</footer>
<article>
  <footer>Related links</footer>
</article>
eu icon getwcag

Trusted by organizations across Europe working toward WCAG and EAA conformance