test-keyboard-navigation
Test a web journey using keyboard-only navigation for reachability, order, focus, activation, escape, and recovery. Use when checking interactive accessibility without a pointer.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- test-keyboard-navigation
- category
- web
- description
- Test a web journey using keyboard-only navigation for reachability, order, focus, activation, escape, and recovery. Use when checking interactive accessibility without a pointer.
# test-keyboard-navigation
Follow realistic tasks, not a tab-count checklist.
## When to use
- Use for navigation, forms, dialogs, menus, tables, editors, media, checkout, and account flows.
- Do not remove focus outlines or add positive tabindex to repair visual order.
## Procedure
1. Define browser, viewport, user state, route, task, expected controls, and accessibility baseline.
2. Start at the address bar and use Tab, Shift+Tab, Enter, Space, arrows, Escape, and documented shortcuts.
3. Verify skip links, logical order, visible focus, no traps, and no offscreen or inert focus.
4. Test custom controls against expected keyboard patterns.
5. Open and close overlays, confirm focus entry, containment where required, return, and background protection.
6. Complete validation and error recovery without a pointer.
7. Repeat at zoom, responsive layouts, and with representative assistive technology.
8. Record steps, affected control, expected behavior, actual behavior, and severity.
## Done
- A keyboard test report records journeys, keys, focus order, visibility, traps, control behavior, and recovery
- Retest verifies fixes across browsers, zoom, responsive layouts, and relevant assistive technology
GitHub에서 보기