aria-roles rule does not support space separated tokens
See original GitHub issueProduct
axe-core
Product Version
4.4.3
Lastest Version
- I have tested the issue with the latest version of the product
Issue Description
In the a11y slack somebody recently asked wether Axe failing space separated token values for the role
attribute is a WCAG or a best practices failure. I assume they used a GUI that doesn’t disclose details, axe-core fails it under WCAG SC 4.1.2.
The axe-core aria-roles rule https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md#wcag-20-level-a--aa-rules
should implement
ACT rule Role attribute has valid value https://act-rules.github.io/rules/674b10
which clearly describes space separated tokens and has a passing test example for it.
Expectation
The ACT rule’s passing test example should not cause a WCAG error in axe-core.
Actual
The ACT rule’s passing test example causes a WCAG error in axe-core.
How to Reproduce
Create a test page that includes the ACT example for a passing test case with space separated tokens in the role
attribute value and use it as input for axe-core.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (2 by maintainers)
Top GitHub Comments
Axe-core fails this because of issues with Internet Explorer. We’re planning to change this fairly soon, since IE is now no longer officially supported.
Validated with the latest axe-core develop branch code base, with the testscript: failing on
but passing when role=“presentation non” (passing role with space seperated text) - as fallbackrole is no longer using