Is this a false positive for ARIA [role = "doc-endnotes"]?
See original GitHub issueLighthouse encounters the following Accessibility error: “Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.” On the page: https://lectupedia.com/en/number-of-books-read-in-each-country/
However, the page contains a <section>
with role="doc-endnotes"
and several children of type <li>
with role="doc-endnote"
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Lighthouse accessibility analysis complains about deprecated ...
Some ARIA parent roles must contain specific child roles to perform their ... Is this a false positive for ARIA [role = "doc-endnotes"]? ......
Read more >Digital Publishing WAI-ARIA Module 1.1 - W3C
This specification defines a set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form ...
Read more >ARIA in HTML - W3C on GitHub
Abstract. This specification defines the authoring rules (author conformance requirements) for the use of and attributes on [ HTML ] ...
Read more >Using ARIA: Roles, states, and properties - MDN Web Docs
ARIA defines semantics that can be applied to elements, with these divided into roles (defining a type of user interface element) and states ......
Read more >doc-endnotes - Accessible Publishing Knowledge Base
The doc-endnotes role from the WAI-ARIA Digital Publishing module. ... The label is identified in the aria-labelledby attribute.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m unsure why this was closed – the issue does not seem to be solved – although I understand it’s a problem with a dependency. At the moment Lighthouse will complain if you pass it the example copied directly from the W3C spec:
I am noticing this with the Axe extension as well so we should move this issue to https://github.com/dequelabs/axe-core. I think https://github.com/dequelabs/axe-core/issues/2759 captures a similar bug.
Interestingly, I came across this which says the violation should be ignored.