跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 accessibility-engineering

Accessibility Engineering

对WCAG 2.2 AA合规性的现有接口进行审计并纠正发现的违规行为。 在审核页面或组件以获取时使用,运行轴心或pa11y,对a11y违规进行分解,或检查屏幕读取器和对比问题后再发送.

官方网址:GitHub

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

对WCAG 2.2 AA合规情况的现有接口进行审计并纠正发现的违规行为

何时用

- 在传送需要进行无障碍审计的用户化变化之前

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Accessibility Engineering、Overview、When to Use、Workflow、Phase 1: Route New UI Work、Phase 2: Run Automated Audit。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/audit-a11y.sh、references/accessibility-checklist.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Audits existing interfaces for WCAG 2.2 AA conformance and remediates the violations found. Use when auditing a page or component for accessibility, running axe-core or pa11y, triaging a11y violations, or checking screen reader and contrast issues before shipping.

Accessibility EngineeringOverviewWhen to UseWorkflowPhase 1: Route New UI WorkPhase 2: Run Automated Auditaxe-core rules through pinned @axe-core/cli (the axe-core package ships no CLI)Keep the JSON for the accessibility-auditorPinned pa11y for HTML validation (WCAG2AA rules via HTML_CodeSniffer)Phase 3: Manual TestingPhase 4: Fix ViolationsCommon Rationalizations

来源分类:GitHub skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
accessibility-engineering
description
Audits existing interfaces for WCAG 2.2 AA conformance and remediates the violations found. Use when auditing a page or component for accessibility, running axe-core or pa11y, triaging a11y violations, or checking screen reader and contrast issues before shipping.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 2
  • scripts/audit-a11y.sh
  • references/accessibility-checklist.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「accessibility-engineering」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-11e16bbb0b1951e9-Accessibility-Engineering.html
请存为 .cursor/skills/accessibility-engineering/SKILL.md 或 .claude/skills/accessibility-engineering/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/addyosmani/agent-skills/tree/HEAD/skills/accessibility-engineering 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/addyosmani/agent-skills/tree/HEAD/skills/accessibility-engineering' --list

npx skills add 'https://github.com/addyosmani/agent-skills/tree/HEAD/skills/accessibility-engineering' --skill 'accessibility-engineering'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: accessibility-engineering description: Audits existing interfaces for WCAG 2.2 AA conformance and remediates the violations found. Use when auditing a page or component for accessibility, running axe-core or pa11y, triaging a11y violations, or checking screen reader and contrast issues before shipping. --- # Accessibility Engineering ## Overview Accessibility is not a polish step — it's a legal requirement in many jurisdictions, an engineering quality standard, and a prerequisite for shipping. This skill audits existing interfaces, triages the findings, and remediates verified violations. The goal is WCAG 2.2 AA compliance supported by automated tools and manual testing. ## When to Use - Before shipping a user-facing change that needs an accessibility audit - When a11y issues are reported (e.g., "screen reader can't read this", "keyboard navigation broken") - When auditing an existing interface for compliance - When triaging axe-core or pa11y findings - When remediating verified accessibility violations **Do NOT use** for building new UI components from scratch; use `frontend-ui-engineering` for construction guidance. Do not use for backend-only changes, CLIs, or library code with no UI output. ## Workflow ### Phase 1: Route New UI Work For component construction, interaction patterns, and focus-management guidance, use `../frontend-ui-engineering/SKILL.md`. Do not restate that skill here. Return to this workflow once an interface exists and needs auditing or remediation. ### Phase 2: Run Automated Audit Execute accessibility checks in this order: ```bash # axe-core rules through pinned @axe-core/cli (the axe-core package ships no CLI) npx --yes @axe-core/[email protected] http://localhost:3000 --exit # Keep the JSON for the accessibility-auditor npx --yes @axe-core/[email protected] http://localhost:3000 --dir ./a11y-reports --save axe.json # Pinned pa11y for HTML validation (WCAG2AA rules via HTML_CodeSniffer) npx --yes [email protected] http://localhost:3000 ``` For a combined report, run `bash skills/accessibility-engineering/scripts/audit-a11y.sh url --json`. It runs both pinned tools, records their status and versions, and fails rather than reporting a clean result when either tool does not produce a valid report. Review the violations grouped by severity: - **Critical** — Blocks screen reader access entirely (missing alt text on info images, empty buttons) - **Serious** — Makes content difficult or impossible to access (low contrast, missing labels) - **Moderate** — Causes confusion or extra effort (heading level skips, redundant ARIA) - **Minor** — Cosmetic or progressive enhancement (missing lang attribute on inner elements) For each violation, verify it's a real issue (not a false positive) by inspecting the element in the browser. ### Phase 3: Manual Testing Automated checks are a smoke test, not proof of conformance. Complete the audit manually. **Keyboard audit:** 1. Tab through every interactive element — can you see where you are? 2. Activate buttons and links with Enter/Space 3. Close modals with Escape 4. Navigate lists with Arrow keys 5. Verify no keyboard traps exist **Screen reader audit (VoiceOver on macOS, NVDA on Windows):** 1. Navigate by heading (VoiceOver: Ctrl+Option+Cmd+H) — is the structure logical? 2. Navigate by landmark (open the rotor with Ctrl+Option+U, choose Landmarks) — are regions labeled? 3. Navigate by link (open the rotor with Ctrl+Option+U, choose Links) — do link descriptions make sense out of context? 4. Interact with a form — are labels announced? Are error messages read? 5. Navigate a dynamic update — are changes announced? **Visual audit:** 1. Verify color contrast (4.5:1 text, 3:1 large text, 3:1 UI components) 2. Zoom to 200% — does layout break or overlap? 3. Test with forced colors / high contrast mode (Windows High Contrast) 4. Reduce motion (prefers-reduced-motion) — are animations disabled? 5. Test focus visibility — is the focus ring visible against all backgrounds? ### Phase 4: Fix Violations For each finding, apply the remediation in order: 1. **Fix the root cause** — Replace a `
` with ``, add ``, set `alt` text 2. **Add ARIA as bridge** — If native HTML can't express the pattern, add ARIA attributes 3. **Test the fix** — Re-run the automated check and manual verification Apply the accessibility checklist (`../../references/accessibility-checklist.md`) as a minimal baseline. ## Common Rationalizations | Rationalization | Reality | |---|---| | "We'll fix a11y later" | Delayed remediation compounds across components and can create legal liability. Audit before shipping. | | "Automated tools caught everything" | Automated checks cannot prove keyboard or screen reader behavior. Manual testing is mandatory. | | "Screen reader users are a tiny minority" | Accessibility is a requirement, not a usage-share calculation. Keyboard navigation, captions, and clear structure also help users across contexts. | | "This is an internal tool, it doesn't need a11y" | Internal tools are subject to the same regulations. Disabled employees and contractors need access. | | "I'll just use aria-label everywhere" | ARIA is a bridge, not a foundation. Semantic HTML first. Overusing ARIA creates maintenance burden and can make things worse. | | "The design system handles accessibility" | Design systems provide accessible primitives. How you compose them determines whether the result is accessible. | | "The audit passed axe-core, so we're done" | Pass axe-core as a smoke test, then test with screen readers and keyboard. A green lighthouse score is not a clean bill of health. | ## Red Flags - Elements that look clickable but aren't keyboard-focusable - Color as the sole indicator of state (red for error, green for success) - Focus outline removed without a visible replacement - Missing labels on form inputs - No heading hierarchy or skipped heading levels - Empty or unlabeled buttons and links - Modals that don't trap focus or restore focus on close - No `alt` text on meaningful images (or `alt=""` missing on decorative ones) - Touch targets that fail SC 2.5.8's 24x24 CSS px size-or-spacing requirement and do not qualify for an exception (AA; 44x44 is the AAA target, SC 2.5.5) - Autoplaying video or audio without controls - Low contrast text (especially on hover, disabled states, placeholders) ## See Also - `../../references/accessibility-checklist.md` — Quick reference for WCAG 2.2 AA - `../frontend-ui-engineering/SKILL.md` — Building accessible components from the start - `../../agents/accessibility-auditor.md` — Dedicated a11y audit persona for deep reviews ## Verification After completing the accessibility workflow: - [ ] Automated audit passes with no Critical or Serious violations - [ ] All interactive elements are keyboard accessible (Tab, Enter, Escape, Arrow keys) - [ ] Screen reader navigation by heading, landmark, and link verified with a named browser + AT pair (or recorded as `manual` and untested — never reported as verified) - [ ] Focus order matches visual order - [ ] Color contrast passes 4.5:1 text / 3:1 large text / 3:1 UI components - [ ] All form inputs have associated labels - [ ] All images have appropriate `alt` text - [ ] Dynamic content changes are announced (aria-live) - [ ] Page is usable at 200% zoom with no content loss - [ ] Touch targets satisfy SC 2.5.8's 24x24 CSS px size-or-spacing requirement or a normative exception (AA); 44x44 is the enhanced AAA target (SC 2.5.5)

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…