Accessibility Test Plan

owl-listener/designer-skills/prototyping-testing/skills/accessibility-test-plan

作者 owl-listener9a6930cf84a8無授權條款2.8K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫4 週前更新

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).

僅含說明Design & Creative
AI 產生的概覽

規劃無障礙測試,涵蓋自動化工具、人工檢查、輔助技術,以及與身心障礙使用者的測試場次。

功能
這項技能會產出結構化的無障礙測試計畫,涵蓋四個測試層面:自動化工具、人工檢查、輔助技術測試,以及有身心障礙人士參與的使用者測試。它為關鍵使用者流程定義測試矩陣,提供依原則與合規等級組織的 WCAG 準則清單,並給出問題回報格式。它也列出最佳實務,例如及早測試並依使用者影響排序。
適用情境
適合在安排或界定無障礙測試範圍時使用,尤其是涉及真實輔助技術使用者的測試場次。它的用途是規劃測試工作,而不是自行評估設計。
執行需求
不需要指令碼或特殊工具,僅為說明性技能。執行該計畫需要能使用無障礙測試工具與輔助技術,並能招募身心障礙參與者。

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

來源與署名

來源:owl-listener/designer-skills位於prototyping-testing/skills/accessibility-test-plan提交9a6930c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架