immersive-web / immersive-web/model-element
Accessibility: ARIA integration and HTML Accessibility API Mappings
Open
Nobody has claimed this yet.
a11y-tracker
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
We need to define how what the ARIA semantics are and what is exposed (application probably). We need to coordinate with the accessibility folks + get this added to the HTML Accessibility API Mappings.
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
Start by clarifying the ARIA semantics for the element and what should be exposed through the application accessibility API. Review the HTML Accessibility API Mappings and coordinate with the accessibility experts identified in the issue. Done means the semantics and exposure are agreed and added to the relevant HTML AAM guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100