3.5.1 landmark-no-duplicate-contentinfo Issue
See original GitHub issueExample structure that is failing when using CLI and API v3.5.1 (not browser extension)
<body>
<header></header>
<nav></nav>
<main>
<article>
<header></header>
<section></section>
<section></section>
<footer></footer>
</article>
</main>
<footer></footer>
</body>
Expectation: Allow <section>, <article>, <aside>, <main>, and <nav> elements to have scoped <footer> element and pass tests; especially when the landmarks are uniquely labeled.
The HTML footer element defines a contentinfo landmark when its context is the body element.
https://www.w3.org/TR/wai-aria-practices/examples/landmarks/contentinfo.html See “HTML Techniques” https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Contentinfo_role See “Best Practices”
Actual: Best practices Error for multiple contentinfo landmarks when there is only one that is a child of body. Violation of “landmark-no-duplicate-contentinfo” with 1 occurrences! https://dequeuniversity.com/rules/axe/3.5/landmark-no-duplicate-contentinfo (Also, will say only 1 occurrence when there is multiple and complains one at a time)
Motivation: To follow HTML5 spec and behave the same as <header> and role banner
https://dequeuniversity.com/rules/axe/3.5/landmark-no-duplicate-banner
axe-core version: 3.5.1
`Running axe-core 3.5.1 in chrome-headless`
axe-webdriver, extension or other integration version: N/A
Browser and Assistive Technology versions N/A
For Tooling issues:
- Node version: v13.8.0
- Platform: Mac
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)

Top Related StackOverflow Question
Correct. The changes have not been released yet. When axe 3.5.3 is released this bug will be fixed.
@dmlb we just released axe-core@3.5.3. This fix should be included.