Audit accessibility of the devguide
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 12
Description
Audit our devguide for assistive tech and ARIA support.
From @hugovk:
Nice little shortcut, but I'm concerned this will interfere with keyboard handling for people using assistive tech such as screen readers.
https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/ includes:
So, screen reader users will commonly expect that pressing the right arrow key will expand a collapsed node.
https://webaim.org/techniques/keyboard/ has examples where ←/→ keys are needed.
Originally posted by @hugovk in https://github.com/python/devguide/issues/1784#issuecomment-4275849620
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
Begin by reviewing the devguide's relevant interactive navigation against the WAI-ARIA keyboard-interface guidance and WebAIM keyboard examples linked in the issue. Identify accessibility and keyboard-handling gaps, then document or implement the required changes and verify that assistive-technology users can operate the affected controls.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100