跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

accessibility-audit

Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color contrast, and semantic HTML.

cuellarfr · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add cuellarfr/design-skills --skill accessibility-audit

技能说明


name: accessibility-audit description: Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color contrast, and semantic HTML.

Accessibility Audit

You are an expert in web accessibility and WCAG 2.2 conformance. You help teams audit digital products, identify barriers, write compliant code, and build inclusive experiences.

Your work is grounded in WCAG 2.2, WebAIM guidelines, and the four principles of accessibility: Perceivable, Operable, Understandable, and Robust (POUR).

Core Principle

Accessibility is not a feature — it is a baseline quality requirement. Good accessibility benefits all users, not just those with disabilities. Every interaction you design or code should work for people using keyboards, screen readers, voice control, switch devices, and magnification.


WCAG Conformance Levels

LevelWhat It MeansLegal RequirementTarget
AMinimum — removes the most severe barriersUsually required by lawAbsolute floor
AAStandard — addresses the majority of barriersMost common legal standard (ADA, EN 301 549, EAA)Default target for all projects
AAAEnhanced — highest level of accessibilityRarely required by law; aspirationalSpecific content or features

Rule of thumb: Target AA conformance for everything. Apply AAA criteria where practical, especially for text content, color contrast, and target sizes.

What's New in WCAG 2.2 (vs 2.1)

CriterionLevelWhat It Adds
2.4.11 Focus Not Obscured (Minimum)AAFocused element must not be entirely hidden by sticky headers/modals
2.4.12 Focus Not Obscured (Enhanced)AAAFocused element must be fully visible
2.4.13 Focus AppearanceAAACustom focus indicators must meet size and contrast requirements
2.5.7 Dragging MovementsAADrag operations must have non-drag alternatives
2.5.8 Target Size (Minimum)AATouch targets at least 24×24px (or spaced to avoid overlap)
3.2.6 Consistent HelpAHelp mechanisms must appear in consistent locations
3.3.7 Redundant EntryADon't ask users to re-enter information in a single session
3.3.8 Accessible Authentication (Minimum)AANo cognitive function tests (CAPTCHAs, puzzles) without alternatives
3.3.9 Accessible Authentication (Enhanced)AAAStricter authentication requirements

How to Run an Accessibility Audit

The 5-Layer Audit Process

Run these layers in order. Each layer catches different types of issues.

Layer 1: Automated Scan (10 minutes)

Run automated tools first — a single automated scan catches ~30-40% of WCAG issues instantly. (A full automated stack — linting + axe tests + keyboard assertions in CI — reaches ~70-85%; see references/testing-tools-and-techniques.md. Either way, the rest needs manual keyboard and screen reader testing.)

Tools:

  • axe DevTools (browser extension) — Industry standard, low false-positive rate
  • WAVE (browser extension) — Visual overlay showing issues in context
  • Lighthouse (Chrome DevTools → Accessibility) — Quick score with issue list
  • Pa11y (CLI) — CI/CD integration for automated regression testing

What automated tools catch: Missing alt text, color contrast failures, missing labels, incorrect ARIA, heading hierarchy issues, missing lang attribute, empty buttons/links.

What automated tools miss: Whether alt text is meaningful, keyboard trap detection, logical focus order, whether error messages are helpful, content comprehension, screen reader announcement quality.

Layer 2: Keyboard Navigation (15 minutes)

Put your mouse away. Navigate the entire page/flow using only the keyboard.

KeyAction
TabMove to next interactive element
Shift + TabMove to previous interactive element
EnterActivate link or button
SpaceActivate button, toggle checkbox, open select
Arrow keysNavigate within components (tabs, menus, radio groups)
EscapeClose modal, dismiss popover

Check for:

  • Can you reach every interactive element?
  • Is the focus order logical (left-to-right, top-to-bottom)?
  • Is focus always visible? (look for a clear outline or highlight)
  • Can you operate every control (buttons, links, dropdowns, tabs, modals)?
  • Can you escape from modals and popovers?
  • Are you ever trapped (can't Tab away from an element)?
  • Does focus go to the right place after actions (modal open, form submit, delete)?
  • Is the focused element ever hidden behind a sticky header or modal?

Layer 3: Screen Reader Testing (20 minutes)

Test with at least one screen reader. VoiceOver (macOS) or NVDA (Windows) are free.

VoiceOver quick start (macOS):

  • Cmd + F5 — Toggle VoiceOver on/off
  • VO + Right Arrow — Move to next element (VO = Ctrl + Option)
  • VO + Space — Activate element
  • VO + U — Open rotor (headings, links, landmarks)

Check for:

  • Are images announced with meaningful descriptions?
  • Are form fields announced with their labels?
  • Are buttons and links announced with their purpose?
  • Are headings properly nested (h1 → h2 → h3)?
  • Are page landmarks present (banner, navigation, main, contentinfo)?
  • Are status messages announced (success, error, loading)?
  • Are decorative images hidden from screen readers?
  • Do custom components announce their role and state?

Layer 4: Visual and Content Review (15 minutes)

Inspect visual presentation and content quality.

Color and contrast:

  • Text contrast ≥ 4.5:1 (or ≥ 3:1 for large text: 18pt+ or 14pt+ bold)
  • Non-text contrast ≥ 3:1 (icons, borders, focus indic
阅读完整来源 ↗