building-accessible-ui Skill
MUST BE USED for any UI work. Invoke this skill before generating, modifying, or reviewing any code that renders, styles, or wires up a user-facing interface — including markup, components, templates, styles, and the JavaScript/TypeScript that drives them. This skill encodes the accessibility (WCAG 2.2 AA) requirements Published by microsoft in a11y-llm-eval.
What is building-accessible-ui Skill?
MUST BE USED for any UI work. Invoke this skill before generating, modifying, or reviewing any code that renders, styles, or wires up a user-facing interface — including markup, components, templates, styles, and the JavaScript/TypeScript that drives them. This skill encodes the accessibility (WCAG 2.2 AA) requirements Published by microsoft in a11y-llm-eval. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Design and media
- Security review use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use building-accessible-ui Skill
- Use it for security review.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/a11y-llm-eval
- Skill file: config/skills/building-accessible-ui/SKILL.md
What it does
MUST BE USED for any UI work. Invoke this skill before generating, modifying, or reviewing any code that renders, styles, or wires up a user-facing interface — including markup, components, templates, styles, and the JavaScript/TypeScript that drives them. This skill encodes the accessibility (WCAG 2.2 AA) requirements
Skill instructions
building-accessible-ui Checklist for producing and reviewing accessible UIs. Each rule leads with the platform-agnostic principle and, where relevant, the Web (HTML + ARIA + CSS) implementation. Apply the web guidance only when the output is web. Detailed rationale lives in references/; widget-specific guidance in components/. Open a file only when it's relevant to the current task. Do not preload. Every file opened and every line a tool prints stays in context — don't re-read. Accessibility constitution Ground rules. Use them to resolve conflicts and decide how much custom work is justified. The checklist below is their mechanical application. 1. Accessibility is a core outcome A UI inaccessible to realistic users is not "done". Treat accessibility as a first-class criterion alongside correctness, performance, and security — not a finishing step. When scope must be cut, record the gap explicitly. Never claim output is "fully accessible"; state what was addressed and known limitations.
Explore related resources
Frequently asked questions
What is building-accessible-ui?
building-accessible-ui is a open-source AI agent skill with Copy skill directory. MUST BE USED for any UI work. Invoke this skill before generating, modifying, or reviewing any code that renders, styles, or wires up a user-facing interface — including markup, components.
Who is building-accessible-ui best for?
building-accessible-ui is best for reusing agent instructions, scripts, and references, security review workflows, design and media workflows.
How do I install building-accessible-ui?
Install or run building-accessible-ui using Copy skill directory. Check building-accessible-ui for the latest setup command.
Is building-accessible-ui actively maintained?
building-accessible-ui may need a closer maintenance check before production use.
Auto-fetched from GitHub.
