Keyboard walk reports complete when focus is trapped
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- playwright, typescript
调研方向
Start with cycle detection in src/providers/keyboard-walk/, where a repeated stop currently ends the walk as complete. Then open the real-browser tests /light-trap and /shadow-trap, which assert no findings for this trapped case. Done means a walk that loops back to an earlier stop without reaching the document body ends with a truncation gap, and those tests are updated to expect it. Whether to also add a separate WCAG 2.1.2 check is a design question to settle with maintainers first.
由索引模型根据 Issue 内容生成。
描述
What happens
When keyboard focus is trapped in a group of controls, the keyboard walk ends as complete. It reports no finding and no gap. The controls after the trap are never reached, but the run reads as if the walk covered the page.
Example: a page with a focus trap around two buttons, followed by an "Outside" button. Tab moves between the two trapped buttons only. The walk sees a repeated stop, ends the cycle, and reports complete. "Outside" is never visited.
There is no keyboard trap rule in src.
Expected
A walk that returns to an earlier stop without passing through the document body has not covered the page. At minimum it should end with a truncation gap. A dedicated keyboard trap check (WCAG 2.1.2 No Keyboard Trap) would report it as a barrier.
Where
src/providers/keyboard-walk/(cycle detection)- The real-browser tests
/light-trapand/shadow-trapcurrently assert no findings for this case.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 8 小时 39 分钟
- 30 天内合并 PR
- 52
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
usabl-dev/usabl 的其他 Issue
-
area: engine enhancement performance
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
area: engine bug
难度 3/5 1-2 天 新手友好度 52/100
维护者通常 1 天内回复
-
area: engine bug
难度 3/5 1-2 天 新手友好度 62/100
维护者通常 1 天内回复
-
area: engine enhancement performance
难度 4/5 1-2 天 新手友好度 45/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
appandflow/stim#5258 ·
维护者通常 1 天内回复
-
area/docs framework/hugo help wanted language/markdown
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 68/100
lingdojo/kana-dojo#33660 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
drizzle-team/drizzle-orm#6639 ·
维护者通常 4 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 76/100