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 从公开仓库中收录这些内容。

举报或申请下架