docs: accessibility audit for framework tracker
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- playwright, typescript
- 领域
- accessibility, frontend, testing
调研方向
Start by reviewing the component tests mentioned in #759 and how the built site and CI are configured. The issue suggests running @axe-core/playwright across built pages, then manually checking chart alternatives, screen reader tables, keyboard access to tooltips and controls, and both themes. Done means agreeing on an audit approach and fixing or triaging the findings; no specific files or completion criteria are named.
由索引模型根据 Issue 内容生成。
描述
suggestion: it might be worth doing a proper accessibility audit of the site at some point.
astro's dev toolbar already has an audit app that flags a11y issues while you browse in dev, which is nice, but it only covers the surface: a limited set of rules, only on the page you have open, and only while running astro dev. the component tests from #759 also run axe, but on each component on its own, so they miss things you only get on real pages like landmarks and headings, colour contrast with the actual theme, or the charts once they're mounted in context.
a few ideas on how we could approach it:
- run axe (
@axe-core/playwright) over every page of the built site in ci, so issues show up on prs instead of whenever someone opens the toolbar - go through what it finds and fix or triage it
- do a manual pass on what tools can't judge: text alternatives for the charts, the screen reader tables, keyboard access to tooltips and the chart controls, both themes
automated checks only catch part of wcag issues, so the manual pass is probably where most of the value is. open to other ideas or tools if anyone has experience with this.
- 主要语言
- TypeScript
- 星标
- 42
- 派生
- 16
- 平均合并
- 12 小时 36 分钟
- 30 天内合并 PR
- 151
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
e18e/framework-tracker 的其他 Issue
-
Interaction Breakdown Chart Colours可能已有人在做 @AlexanderKaran 于 2 天前认领。 未关闭documentation enhancement
难度 2/5 1-3 小时 新手友好度 48/100
e18e/framework-tracker#771 ·
维护者通常 1 天内回复
-
Depot Logo未关闭bug enhancement
难度 3/5 1-2 天 新手友好度 56/100
e18e/framework-tracker#768 ·
维护者通常 1 天内回复
-
Improve Tables未关闭documentation enhancement
难度 4/5 3-5 天 新手友好度 48/100
e18e/framework-tracker#766 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
e18e/framework-tracker#760 ·
维护者通常 1 天内回复
-
enhancement maintenance
难度 4/5 3-5 天 新手友好度 48/100
e18e/framework-tracker#759 ·
维护者通常 1 天内回复
查看 e18e/framework-tracker 的全部 Issue
相似的 Issue
-
check:passed streams:add
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
bug implicit-state
难度 2/5 1-3 小时 新手友好度 76/100
-
book-layout.spec fails when the similar-books rail holds other projects' books可能已有人在做 @praetorianer777 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
praetorianer777/GoTome#373 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
Tencent/tdesign-react#4465 · 1 条评论 ·
维护者通常 1 天内回复
-
area:cards enhancement ready-for-agent
难度 2/5 1-3 小时 新手友好度 66/100
fil-donadoni/tolaria#8883 ·
维护者通常 1 天内回复