$ ~/registry/skill/microsoft-github-skills-accessibility-accessibility

SKILL

accessibility

帮你按无障碍标准评估页面并生成整改方案

来源

GitHub

更新于

2026-08-21

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "accessibility" 技能：
1. 下载 https://raw.githubusercontent.com/microsoft/hve-core/main/.github/skills/accessibility/accessibility/SKILL.md
2. 保存为 ~/.claude/skills/accessibility/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

检查页面无障碍问题

输入

请基于 WCAG 2.2、ARIA APG 和 Section 508，帮我梳理这个页面可能的无障碍问题，并按优先级列出整改建议。

预期产出

输出一份按优先级排序的问题清单和整改建议。

走 Accessibility Planner 流程

输入

请按 Accessibility Planner 的六个阶段，先帮我完成 Discovery 和 Framework Selection，再说明后续阶段需要准备什么信息。

预期产出

输出阶段化的问答引导和后续所需材料。

生成扫描命令

输入

我想扫描一个本地 HTML 页面，请给我使用脚本的示例命令，并说明运行前需要哪些前置条件。

预期产出

输出可执行的扫描命令和运行前提说明。

// 适用场景

页面上线前做无障碍检查

开发者或设计师在页面上线前，需要快速了解可能不符合无障碍标准的地方。这个技能可用于参考 WCAG、ARIA APG、Section 508 等标准并组织整改思路。

推进 Accessibility Planner 流程

产品或项目推进无障碍工作时，可以按六个阶段推进：发现、框架选择、标准映射、风险评估、影响与证据、交接。

运行扫描并规范结果

当需要检查 URL 或本地页面时，可使用脚本入口调用扫描流程，并得到稳定的 JSON 结果格式。

// 文档

AI 摘要

这份文档定义了 accessibility 技能的统一入口，说明其负责无障碍框架引用解析、Accessibility Planner 六阶段流程以及扫描 CLI 的使用方式。文档列出 WCAG 2.2、ARIA APG、认知无障碍、Section 508 和 EN 301 549 等参考框架，并给出扫描脚本的前置条件与示例命令。

展开完整文档 ▾

Accessibility — Skill Entry

This skill is the canonical accessibility reference contract for HVE Core. Agents and instructions invoke this skill by name and rely on it to own framework reference resolution, phase guidance resolution, and the scanner CLI entrypoint.

Framework references

WCAG 2.2
ARIA Authoring Practices Guide
Cognitive Accessibility Guidance
Section 508
EN 301 549

Accessibility Planner workflow

The Accessibility Planner runs six phases, each keyed to a state id:

Phase 1 — Discovery (discovery)
Phase 2 — Framework Selection (framework-selection)
Phase 3 — Standards Mapping (standards-mapping)
Phase 4 — Plan Risk Assessment (plan-risk-assessment)
Phase 5 — Impact and Evidence (impact-evidence)
Phase 6 — Backlog Handoff (backlog-handoff)

Phase reference index

Phase 1 — Discovery: capture-coaching.md — read this when running exploration-first capture questioning.
Phase 2 — Framework Selection: framework-selection.md — read this when choosing which frameworks and conformance level apply.
Phase 3 — Standards Mapping: walk the framework references roll-up tables to emit controlMappings; consumed by Phase 5. No dedicated file — mapping is driven by the framework roll-ups.
Phase 4 — Plan Risk Assessment: capture-coaching.md governs the questioning posture when escalation triggers reopen scoping; tier criteria are applied per the Accessibility Planner identity instructions and recorded as riskClassification.tier. No dedicated file — the accessibility risk surface is narrow enough to stay inline.
Phase 5 — Impact and Evidence: impact-assessment.md — read this when building the evidence register, tradeoff log, and seed work-items.
Phase 6 — Backlog Handoff: backlog-handoff.md — read this when rendering work items and validating handoff gates.

Tooling

The scanner CLI (scripts/scan.py) wraps the Node-based axe-core scanner and normalizes its findings into a stable JSON shape.

Prerequisites

Python 3.11+ with uv available on PATH.
Node.js with npx available on PATH.
Network access on first run so npx can fetch @axe-core/cli.

Quick Start

uv run scripts/scan.py https://example.com
uv run scripts/scan.py ./page.html --output results.json

Parameters Reference

Parameter	Required	Default	Description
`target`	Yes	—	URL or local file to scan.
`--output`	No	stdout	Path to write the normalized JSON results.

Script Reference

Entrypoint: scripts/scan.py

Output shape:

{
  "target": "<scanned target>",
  "summary": {
    "violations": 0,
    "passes": 0,
    "incomplete": 0,
    "inapplicable": 0
  },
  "violations": [
    { "id": "", "impact": "", "description": "", "nodes": 0 }
  ]
}

Exit codes:
- 0 — scan completed successfully.
- 1 — scan failed or returned invalid output.
- 2 — scanner unavailable (Node.js or @axe-core/cli missing).