github / github/annotation-toolkit
[Feature request] Split and refine the Mobile accessibility checklist
- 主要语言
- 没有语言数据
- 星标
- 320
- 派生
- 33
- 平均合并
- 36 分钟
- 30 天内合并 PR
- 2
描述
### Description
The first version of the Mobile accessibility checklist is now live in the [repository](https://github.com/github/annotation-toolkit/blob/main/checklists/mobile-checklist.md) and on the [primer.style docs site](https://primer.style/accessibility/tools-and-resources/checklists/mobile-checklist/) (shipped via #41, closing #36).
In practice, the mobile checklist ended up about twice as long as the existing web checklists. That length makes it harder to scan and harder to hand to a single audience without a lot of "skip this section" caveats. This issue tracks the follow-up edits and improvements needed to bring it in line with the rest of the toolkit.
### Requested change
Refactor the Mobile checklist into multiple, more focused variants, mirroring how the web checklists are split today:
- **Split by audience:** Separate the content into a mobile **designer** checklist and a mobile **engineer** checklist, so each role only sees items relevant to their phase of work.
- **Split by depth:** Offer a **full** checklist (the comprehensive list we have now) and a **high-impact** short list that surfaces the most critical items for teams who can't run through the full thing on every project.
- **Rebuild the Figma component:** Update the Checkpoints component in the Figma library so the new variants are selectable as properties, consistent with the existing web checklist component. This is a heavier lift than the markdown work since the current
贡献指南
调研方向
Start with checklists/mobile-checklist.md and compare it with the existing web checklists to define designer, engineer, full, and high-impact variants. Then inspect the Checkpoints component in the Figma library and the work shipped in #41; done means the markdown variants are usable without skip-section caveats and the Figma component exposes the new variants as selectable properties.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- figma
- 领域
- accessibility, design, documentation
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100