Product
axe-core
Product Version
4.6.3
Latest Version
Issue Description
Expectation
The focus-order-semantics rule should not raise a violation for an element in the focus order with role="article" since it's listed as one of the allowable roles at https://dequeuniversity.com/rules/axe/4.6/focus-order-semantics.
Actual
Running axe on an element such as <div role="article" tabindex="0"> creates a focus-order-semantics violation.
How to Reproduce
- Open https://codepen.io/philipjia123-the-reactor/full/ZEjNWZe
- Run axe with experimental rules enabled
- Observe that a
focus-order-semantics violation is produced
Additional context
This seems to be an issue with the article role being omitted from the VALID_ROLES_FOR_SCROLLABLE_REGIONS list:
|
const VALID_ROLES_FOR_SCROLLABLE_REGIONS = { |
|
application: true, |
|
banner: false, |
|
complementary: true, |
|
contentinfo: true, |
|
form: true, |
|
main: true, |
|
navigation: true, |
|
region: true, |
|
search: false |
|
}; |
even though the corresponding tag name is included
|
const VALID_TAG_NAMES_FOR_SCROLLABLE_REGIONS = { |
|
ARTICLE: true, |
|
ASIDE: true, |
|
NAV: true, |
|
SECTION: true |
|
}; |
Happy to put in a quick pull request, just wanted to make sure this is actually a bug.
Product
axe-core
Product Version
4.6.3
Latest Version
Issue Description
Expectation
The
focus-order-semanticsrule should not raise a violation for an element in the focus order withrole="article"since it's listed as one of the allowable roles at https://dequeuniversity.com/rules/axe/4.6/focus-order-semantics.Actual
Running axe on an element such as
<div role="article" tabindex="0">creates afocus-order-semanticsviolation.How to Reproduce
focus-order-semanticsviolation is producedAdditional context
This seems to be an issue with the
articlerole being omitted from the VALID_ROLES_FOR_SCROLLABLE_REGIONS list:axe-core/lib/checks/aria/valid-scrollable-semantics-evaluate.js
Lines 18 to 28 in 3dcdd42
axe-core/lib/checks/aria/valid-scrollable-semantics-evaluate.js
Lines 7 to 12 in 3dcdd42
Happy to put in a quick pull request, just wanted to make sure this is actually a bug.