dequelabs / dequelabs/axe-core
Add "radiogroup should have an accessible name" as a best practice
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 933
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 29
Description
### Product
axe-core
### Feature Description
Hi axe-core folks, I am opening a new issue in the vein of https://github.com/dequelabs/axe-core/issues/3256.
I would like to be alerted when elements with `role="radiogroup"` don't have a name that can be programmatically determined. I like [this suggestion](https://github.com/dequelabs/axe-core/issues/3256#issuecomment-999811865) of adding this as a best practice instead of a violation, given that WCAG and WAI-ARIA treat this requirement differently.
Even though a11ysupport.io marks this feature as only ["partially supported"](https://a11ysupport.io/tests/tech__aria__aria-required-radiogroup#assertion-aria-radiogroup_role-convey_name--jaws-chrome) by JAWS, drilling down into the specifics shows that JAWS consistently knows about the radiogroup's name. This broad support makes "radiogroup should have a name" a strong candidate for being represented somehow in `axe-core`.
If this sounds generally good, I can fill out a new rule template.
Contributor guide
Research direction
Start by reviewing the linked axe-core issue 3256 and its suggestion about treating this as a best practice. Then examine the new rule template mentioned in the issue. Done means reaching agreement on the rule's scope and adding a corresponding axe-core rule with the expected behavior covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100