python / python/docs-community
Feature: Add right/left n/p keyboard navigation to all Python docs
还没有人认领这个 Issue。
- 主要语言
- Makefile
- 星标
- 55
- 派生
- 26
- PR 合并指标
- 30 天内没有已合并 PR
描述
Describe the enhancement or feature you would like
Right now the accessibility audit https://github.com/python/devguide/issues/1792 is blocking keyboard navigation https://github.com/python/devguide/pull/1784 not only for devguide, but across Python ecosysem https://github.com/orgs/sphinx-doc/discussions/14406 https://github.com/sphinx-doc/sphinx/pull/14408 https://github.com/readthedocs/sphinx_rtd_theme/pull/1686 https://github.com/pradyunsg/furo/discussions/932
Clearly, other projects may not have the resources to access the risk of hurting sensitive auditory, so all maintainers just don't take it - and while Sphinx comes with keyboard shortcuts, no project across Pyto ecosystem enables it.
Now that there is a chance to do accessibility study, please make sure that both arrow keys and vim `style n/p keys are evaluated for usage, with official "documentation accessibility" chapter, that could be easily referenced for other projects to follow.
Thanks for your time, folks.
Describe alternatives you have considered
No response
Additional context
No response
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先审阅链接的无障碍审计、devguide 导航拉取请求以及 Sphinx 生态系统中的讨论,以了解其中指出的风险和现有方法。确定官方文档无障碍章节的范围,以及应如何在各个 Python 文档项目中评估箭头键导航和 vim 风格的 n/p 导航;完成后应提供其他维护者可以参考的指导。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- accessibility, documentation
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100