AccessKit / AccessKit/accesskit
How closely to follow the WAI-ARIA roles spec/naming?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
I know next to nothing about the W3C specs, but it seems like there's a standard for accessibility roles on elements:
https://www.w3.org/TR/wai-aria/
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles
@mwcampbell noted at the RustWeek Rust UI & App Dev Unconf that he's leaning towards diverging from the naming in these? I'd like to make the argument that this is probably the wrong choice, for the single reason that the web is huge, has had thousands if not hundreds of thousands of working directly om it, and having similar naming makes things much more approachable for newcomers to the space.
For a similar example, Winit has adopted both keyboard-types and cursor-icon which are based on W3C specs, ui-events is based on W3C specs, and so on.
WDYT?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the WAI-ARIA specification and the MDN ARIA roles reference linked in the issue, then compare their naming with the naming direction discussed for AccessKit. The issue is complete only after the project reaches a decision on whether its role names should follow those standards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100