accessibility Skill
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow. Published by microsoft in hve-core.
Decision snapshot
Is this a fit?
Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is accessibility Skill?
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow. Published by microsoft in hve-core. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Declared skill metadata
- Declared license: MIT
- Compatibility: Requires Python 3.11+ and uv; the scanner additionally needs Node.js and network access to run 'npx --yes @axe-core/cli@4.12.1'.
- Source file: .github/skills/accessibility/accessibility/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use accessibility Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/hve-core
- Skill file: .github/skills/accessibility/accessibility/SKILL.md
What it does
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
Skill instructions
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 Graphics ARIA and SVG-AAM Assessment reference (cross-cutting, not a conformance framework): Assistive-technology announcement model — read this when deciding the announcement-class criteria (WCAG 1.3.1, 4.1.2, 4.1.3): what a screen-reader user should hear, and how to decide it with an accessibility-tree assertion or a manual AT pass. Accessibility Planner workflow The Accessibility Planner runs six phases, each keyed to a state id: 1. Phase 1 — Discovery (discovery) 2. Phase 2 — Framework Selection (framework-selection) 3. Phase 3 — Standards Mapping (standards-mapping) 4. Phase 4 — Plan Risk Assessment (plan
Verified compatibility and discovery
Frequently asked questions
What is accessibility?
accessibility is a open-source AI agent skill with Copy skill directory. Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
Who is accessibility best for?
accessibility is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install accessibility?
Install or run accessibility using Copy skill directory. Check accessibility for the latest setup command.
Is accessibility actively maintained?
accessibility may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
