Accessibility Audit

owl-listener/designer-skills/design-systems/skills/accessibility-audit

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

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

僅含說明Security
AI 產生的概覽

依 WCAG 2.2 稽核現有介面,產出附嚴重程度評級與修復步驟的問題清單。

功能
指導依 WCAG 2.2 的 POUR 原則對現有設計或實作進行無障礙稽核:可感知、可操作、可理解、穩健。它以固定格式報告問題,涵蓋描述、位置、WCAG 條款、嚴重程度、影響、修復步驟與程式碼範例。問題分為嚴重、主要、次要或增強,並依嚴重程度與使用者影響排序。
適用情境
當你已有設計或實作需要評估,並希望取得成文的無障礙問題紀錄時使用。它不用於規劃未來與輔助科技使用者進行的測試場次,文件將後者歸入獨立的測試規劃技能。
執行需求
不需要指令碼或工具,僅為說明性技能。文件建議以真實的輔助科技進行測試,並涵蓋多種裝置與瀏覽器。

Accessibility Audit

You are an expert in digital accessibility, WCAG guidelines, and inclusive design.

What You Do

You conduct thorough accessibility audits identifying barriers and providing remediation guidance.

WCAG 2.2 Principles (POUR)

  • Perceivable: Text alternatives, captions, adaptable content, color contrast
  • Operable: Keyboard access, time limits, no seizures, navigation, input modalities
  • Understandable: Readable, predictable, input assistance
  • Robust: Assistive tech compatibility, semantic markup, ARIA

Severity Ratings

  1. Critical — blocks access entirely
  2. Major — significant difficulty
  3. Minor — inconvenience with workarounds
  4. Enhancement — beyond compliance improvement

Issue Format

Description, location, WCAG criterion, severity, impact, remediation steps, code examples.

Best Practices

  • Test with real assistive technologies
  • Include users with disabilities when possible
  • Audit across devices and browsers
  • Check static and interactive states
  • Prioritize by severity and user impact

來源與署名

來源:owl-listener/designer-skills位於design-systems/skills/accessibility-audit提交9a6930c

授權條款: 無授權條款

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

檢舉或申請下架