360 Secure SkillHub
360 安全技能中心

accessibility-test-plan

该 Skill 提供无障碍测试计划指导，覆盖自动化、手动与辅助技术测试，规划参与者标准、测试矩阵、WCAG 检查清单、问题报告与最佳实践；不包含实际审计、执行测试或招募参与者。

Owl-Listener
热度 24.09
最近更新 2026-10-19 04:18:10
分类：开发依赖：纯提示词应用场景：工作流 / 报告撰写 / 模板 / 日程安排

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add owl-listener/designer-skills/accessibility-test-plan
Metadata
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