question-mark
Stuck on an issue?

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.

aria-roles rule does not support space separated tokens

See original GitHub issue

Product

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:closed
  • Created a year ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
WilcoFierscommented, Aug 17, 2022

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.

0reactions
padmavemulapaticommented, Oct 10, 2022

Validated with the latest axe-core develop branch code base, with the testscript: failing on

<div role="doc-biblioentry" id="fail1">fail</div>
  <div role="doc-endnote" id="fail2">fail</div>

but passing when role=“presentation non” (passing role with space seperated text) - as fallbackrole is no longer using

<div role="presentation none" id="pass2"></div>
  <div role="button alert" id="pass1">fail</div>

Image

Read more comments on GitHub >

github_iconTop Results From Across the Web

Role attribute has valid value[proposed] | ACT Rule | WAI - W3C
The role attribute is a set of space separated tokens. ... If the first token is not accessibility supported (or valid), the next...
Read more >
Add check to fail fallback roles #724 - GitHub
The attribute, if specified, must have a value that is a set of space-separated tokens; each token must be a non-abstract role defined...
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 >
SIA-R21 role attributes have a valid value - Rules - Siteimprove
This rule checks that each role attribute has a valid value. ... which is specified as a set of space-separated tokens, corresponds to...
Read more >
Notes on use of multiple ARIA role attribute values - TPGi
The attribute, if specified, must have a value that is a set of space-separated tokens representing the various WAI-ARIA roles that the ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found