immersive-web / immersive-web/model-element
Accessibility of model
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
We need to figure out how to make <model> accessible on a number of different fronts:
- Visual: describe what is being presented over time.
- Interaction: describe what can interacted with (regions, buttons, etc.).
- auditory: describe audio and possibly spoke sounds, potentially over time.
Usually, this would be provide by the embedded format... however, it appears that both glTF and USDZ are quite limited when it comes to accessibility.
As such, it may be that we need to leverage what we can from HTML + ARIA to overcome the shortcomings of these formats. We have quite a bit of precedent (e.g., from the humble, yet limited, alt attribute, to how <canvas> can be made accessibly, to the potential inclusion of <track> elements, and so on).
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
The issue names no files or tests; begin by reviewing the accessibility requirements alongside the mentioned glTF, USDZ, HTML/ARIA, canvas, alt, and track precedents. Because it proposes several possible directions without acceptance criteria, establish the concrete scope and definition of done before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100