immersive-web / immersive-web/model-element
model element accessibility requirements
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
model element accessibility requirements...
There are already some examples in the Model Element Explainer
As for model formats, USD in particular allows the model itself to contain accessibility information... (similarly to how an SVG image can contain an accessible subtree or not) so this requirements list isn't limited to simple accessibility like a label on a leaf node.
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 reading the explainer sections on Fallback Content and Playback and accessibility considerations. Then review the linked USD AccessibilityAPI documentation and identify the accessibility requirements the model element should address, including information embedded in model formats; done means a decided requirements list is recorded in the project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100