Accessibility Reports?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
It'd be great to consider a new type of report for a11y issues. There's a handful of things that could probably be detected and reported like autoplaying videos with prefers-reduced-motion, contrast issues, CSS animations when prefers-reduced-motion is set, maybe some common ARIA issues?
Would definitely need some deeper thought into if it would only report "high confidence" issues like poor contrast, or assume that if the developer is opting-in to it, the UA could be more aggressive in reporting all potential issues with enough context for the developer to know which/if any are intentional. (IE - some animations are acceptable with prefers-reduced-motion)
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
No files, tests, or entry points are named. Start by defining which accessibility conditions should be reported and how confidence or developer intent would be represented, then review the existing Reporting API design for the extension point. Done means the scope and reporting behavior are specified well enough to implement and test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- accessibility, api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100