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

SKILL

accessibility

Assess accessibility against standards and generate remediation guidance.

Source

GitHub

Updated

2026-08-21

// securityLow risk

Prompt only, no code
Open source

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "accessibility" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/hve-core/main/.github/skills/accessibility/accessibility/SKILL.md
2. Save it as ~/.claude/skills/accessibility/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Check page accessibility issues

Prompt

Using WCAG 2.2, ARIA APG, and Section 508, identify likely accessibility issues on this page and list prioritized remediation suggestions.

Expected

A prioritized list of accessibility issues and remediation suggestions.

Run the Accessibility Planner workflow

Prompt

Follow the six Accessibility Planner phases, complete Discovery and Framework Selection first, then explain what information is needed for later phases.

Expected

Phase-based guidance and the information needed for later stages.

Generate scan command

Prompt

I want to scan a local HTML page. Give me an example command using the script and explain the prerequisites before running it.

Expected

An executable scan command and the prerequisites to run it.

// use cases

Pre-launch accessibility check

Developers or designers can use it before launch to review likely accessibility gaps. It helps organize remediation against standards such as WCAG, ARIA APG, and Section 508.

Drive the Accessibility Planner workflow

Product or project teams can follow the six-phase Accessibility Planner workflow: discovery, framework selection, standards mapping, risk assessment, impact/evidence, and handoff.

Run scans and normalize results

When checking a URL or local page, teams can use the script entrypoint to run scans and get normalized JSON results.

// docs

AI summary

This document defines the accessibility skill as the canonical entrypoint for framework reference resolution, the six-phase Accessibility Planner workflow, and the scanner CLI. It lists references for WCAG 2.2, ARIA APG, cognitive accessibility, Section 508, and EN 301 549, and includes prerequisites plus example scan commands.

Show full docs ▾

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).

Troubleshooting

Symptom	Likely cause	Action	Exit code

…

View full docs ↗

// FAQ

What does this skill mainly do?

It serves as the unified accessibility entrypoint, covering WCAG 2.2, ARIA APG, cognitive accessibility, Section 508, EN 301 549, and the Accessibility Planner workflow. It also provides a scanner CLI entrypoint for normalized scan results.

What prerequisites are needed to run scans?

You need Python 3.11+, uv on PATH, Node.js, and npx available on PATH. First run also requires network access so npx can fetch @axe-core/cli.

How do I start using the scan script?

The docs show examples such as `uv run scripts/scan.py https://example.com` or scanning a local file with `uv run scripts/scan.py ./page.html --output results.json`. For more parameter details, see the source repository.