Ensure the contentinfo Landmark Is At the Top Level

Web accessibility standards state that the contentinfo landmark must be at the top level.

Why It Matters

When replaced with another landmark, the contentinfo landmark can prevent blind screen reader users from being able to quickly find and navigate to the appropriate landmark.

When screen reader users have to sort through too much extra information to find what they’re looking for, it negates the purpose of an existing contentinfo landmark.

Fixing the Issue

Developers should ensure that any contentinfo landmark is not contained in another landmark.

Text content should be housed within a landmark region, the role=”contentinfo” ARIA landmark should be used on an element that is outside of other landmarks used on the page. This is because footer information is generally separated from the header and main body content.