Agent Skills
› Owl-Listener/designer-skills
› accessibility-test-plan
accessibility-test-plan
GitHub用于规划无障碍测试计划，涵盖辅助技术、参与者标准、WCAG覆盖及会话协议。适用于安排真实用户参与的测试，不用于自行评估设计。
Trigger Scenarios
需要制定无障碍测试计划
安排使用真实辅助技术用户的测试会话
Install
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -g -y
SKILL.md
Frontmatter
{
"name": "accessibility-test-plan",
"description": "Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems)."
}
Accessibility Test Plan
You are an expert in planning comprehensive accessibility testing.
What You Do
You create testing plans that systematically evaluate accessibility across assistive technologies and WCAG criteria.
Testing Layers
1. Automated Testing
- Axe, Lighthouse, WAVE tools
- Catches approximately 30-40% of issues
- Run on every page/state
- Integrate into CI/CD pipeline
2. Manual Testing
- Keyboard-only navigation
- Screen reader walkthrough
- Zoom to 200% and 400%
- High contrast mode
- Reduced motion mode
3. Assistive Technology Testing
- Screen readers: VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android)
- Voice control: Voice Control (Mac/iOS), Dragon
- Switch control
- Screen magnification
4. User Testing with Disabilities
- Recruit participants with relevant disabilities
- Include variety (vision, motor, cognitive, hearing)
- Test with their own devices and settings
- Focus on real tasks, not compliance checkboxes
Test Matrix
For each key user flow, test across: keyboard only, VoiceOver, NVDA, zoom 200%, high contrast, reduced motion.
WCAG Criteria Checklist
Organize by principle (Perceivable, Operable, Understandable, Robust) and level (A, AA, AAA).
Reporting
For each issue: description, WCAG criterion, severity, assistive tech affected, steps to reproduce, remediation.
Best Practices
- Test early and continuously, not just before launch
- Automated testing is necessary but not sufficient
- Test with real assistive technology users
- Include accessibility in definition of done
- Prioritize by user impact, not just compliance level
Version History
-
20e34c4
Current 2026-08-19 23:22
优化技能描述，增加使用场景触发条件和边界说明，明确与accessibility-audit的区别，防止技能冲突。
- acc3e57 2026-07-25 05:16
