Consider adding accessibility considerations for authors
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
WebCodecs is a low-level API, which should not have direct accessibility implications for implementations.
WebCodecs makes it easier for applications to implement their own media player. Built-in media players come with accessibility related features, including the ability to slow or pause playback, support for captions, or switching to an audio description stream. The spec already has a Best Practices for Authors Using WebCodecs section. It could perhaps be completed to include accessibility considerations ("with great powers come great responsibility").
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 with the WebCodecs specification's “Best Practices for Authors Using WebCodecs” section, linked in the issue, and review how applications provide playback controls, captions, and audio descriptions. Done means extending that section with practical accessibility considerations for authors, while keeping the guidance scoped to application use of WebCodecs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100