Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Consider making 'duplicate-id' rule as best practice
See original GitHub issueCurrently duplicate-id rule is tagged as WCAG 4.1.1 and F77 only mentions about how AT experience would be impacted if duplicate IDs are used.
We have tested the various duplicate-id failure scenarios for AT experience i,e. using screen readers like NVDA, JAWS, Narrator and Speech recognition software like Dragon NaturallySpeaking & Windows speech recognition. We found that none of the duplicate-id rule failures have an impact on these ATs and other failures which have an impact on ATs fall into either duplicate-id-aria or duplicate-id-active rule failure categories.
Hence, please consider make the duplicate-id rule a best practice rule
Expectation: Tag duplicate-id rule as best practice
Actual: duplicate-id rule is tagged as WCAG 4.1.1
Motivation: There is no screen readers or speech recognition software experience impact on the elements that fail this rule
axe-core version: 4.1.1 Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@WilcoFiers sure, thanks for the update
I’m going to close this issue. Deque’s official position on this is that duplicate IDs anywhere in a page is a failure of WCAG 2.0, success criterion 4.1.1 Parsing. Axe-core is highly configurable, anyone who would prefer to run axe without this rule can turn it of.