Contentinfo landmark should not be contained in another landmark

Rule ID: landmark-contentinfo-is-top-level
Ruleset: axe-core 4.5
User Impact: Moderate
Guidelines: Deque Best Practice

Need accessibility training?

Deque University offers an extensive curriculum of self-guided online courses for every skillset and experience level.

Compliance Data & Impact

User Impact

Moderate
Minor
Critical

Disabilities Affected

  • Sighted Keyboard Users
  • Blind
  • Deafblind

Standard(s)

  • Deque Best Practice

    How to Fix the Problem

    Ensure any contentinfo landmark is not be contained in another landmark.

    Text content should be contained 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, since footer information is generally separated from the header and main body content.

    Why it Matters

    The purpose of the contentinfo landmark can be defeated when placed within another landmark, as it 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, such as not being able to quickly figure out which landmark contains the content information they're looking for negates the purpose of an existing contentinfo landmark.

    Rule Description

    Contentinfo landmark must be at top level.

    The Algorithm (in simple terms)

    This rule finds the elements for the footer:not([role]) and [role="contentinfo"] selectors, then checks to see if the landmark has a body context.

    Resources

    Other Resources

    You may also want to check out these other resources.

    Refer to the complete list of axe 4.5 rules.

    Was this information helpful?

    You have already given your feedback, thank you..

    Your response was as follows:

    Was this information helpful?
    Date/Time feedback was submitted: