Audit documentation keyboard navigation
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 半天
- 新手友好度
- 84/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript, markdown
调研方向
在 current main 上阅读 docs/astro.config.mjs、docs/src/content/docs/reference/text.md、docs/src/content/docs/guides/deployment.md 和 example.env，然后审查文档站点的侧边栏搜索控件和焦点可见性。创建 docs/src/content/docs/guides/roadmap/keyboard-audit.md，其中包含浏览器详细信息和可复现的发现，仅应用现有的 framework 约定。使用 npm --prefix docs ci、npm --prefix docs run build 和 git diff --check 进行验证。
由索引模型根据 Issue 内容生成。
描述
DOC-17 · Documentation and accessibility
Difficulty: beginner · Status: ready
This is a focused contribution against current main. No unmerged feature PR is required.
Why this is useful
No accessibility verification is recorded
Start here
Source audit: 9d8ac3e01df1. Read these files on current main too, because paths may change after the audit:
docs/astro.config.mjsdocs/src/content/docs/reference/text.mddocs/src/content/docs/guides/deployment.mdexample.env
Scope and intended output
Write docs/src/content/docs/guides/roadmap/keyboard-audit.md; keep this contribution in its own page. Maintainers can add navigation links after merge to avoid concurrent sidebar edits.
Acceptance criteria
- Check sidebar search code controls and focus visibility
- Record browser and reproducible defects
- Fix only within the site's existing framework conventions
Verification
npm --prefix docs ci
npm --prefix docs run build
git diff --check
Build the docs site locally. Verify the described commands against current source; explicitly report platform steps you could not execute. Do not run paid examples as a build check.
Dependencies
None. Keep the PR based on current upstream main.
Out of scope
- Unrelated refactors, broad formatting, endpoint renames, or extra dependencies without agreement.
- Live cloud provisioning, paid model calls, real private messages, or credentials in fixtures/logs.
- Implementing neighboring roadmap issues in the same PR.
Getting help and submitting
Comment with your intended approach and ask when expected behavior is unclear. Check for an existing PR before starting; there is no deadline for a volunteer contribution. A useful reproduction or partial finding is welcome.
Use the issue's criteria as the review checklist. Include the commands actually run and any limitations. Link the issue; use Fixes only when its entire agreed scope is complete. If CONTRIBUTING.md is not yet on main, the contributor-roadmap PR provides the onboarding guide.
- 主要语言
- Python
- 星标
- 3
- 派生
- 10
- 平均合并
- 8 小时 11 分钟
- 30 天内合并 PR
- 18
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ashrafee-dev/scamshield-api 的其他 Issue
-
area:testing contributor-roadmap difficulty:intermediate help wanted status:ready
难度 2/5 1-3 小时 新手友好度 78/100
ashrafee-dev/scamshield-api#291 ·
维护者通常 1 天内回复
-
area:docs contributor-roadmap difficulty:beginner documentation good first issue help wanted status:ready
难度 2/5 半天 新手友好度 84/100
ashrafee-dev/scamshield-api#286 ·
维护者通常 1 天内回复
-
area:docs contributor-roadmap difficulty:beginner documentation good first issue help wanted status:ready
难度 2/5 1-3 小时 新手友好度 86/100
ashrafee-dev/scamshield-api#285 ·
维护者通常 1 天内回复
-
area:docs contributor-roadmap difficulty:beginner documentation good first issue help wanted status:ready
难度 2/5 1-3 小时 新手友好度 88/100
ashrafee-dev/scamshield-api#283 ·
维护者通常 1 天内回复
-
area:docs contributor-roadmap difficulty:beginner documentation good first issue help wanted status:ready
难度 2/5 1-3 小时 新手友好度 88/100
ashrafee-dev/scamshield-api#282 ·
维护者通常 1 天内回复
查看 ashrafee-dev/scamshield-api 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 64/100
agrc/palletjack#208 ·
-
status/needs-triage type/bug
难度 2/5 1-3 小时 新手友好度 85/100
PKU-YuanGroup/OpenAI4S#218 ·
维护者通常 1 天内回复
-
Test Leakage可能已有人在做 @garland3 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 90/100
sandialabs/atlas-ui-3#1030 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 84/100
aws-samples/sample-ai-persona#151 ·
维护者通常 1 天内回复