accessibility
Accessibility (a11y) testing — WCAG checks, keyboard navigation, screen-reader semantics, color contrast.
SKILL.mdskills/web/accessibility/SKILL.md
GitHubAccessibility
Purpose
Audit UI / web content for accessibility. Check against WCAG principles, keyboard navigation, screen-reader semantics, and color contrast.
When to Use
- User wants an accessibility audit
- User is shipping a UI
- User is fixing reported a11y issues
Safety
- Accessibility is a practice, not a checklist
- Include users with disabilities when designing
Source
Custom skill, written for this library.
Notes
Pairs with browser-automation (to run automated checks) and code-review (to enforce standards).
When NOT to Use
Do not use when the request is outside this capability, required context is unavailable, or a safer specialized skill applies.
Capabilities
- Apply the accessibility workflow consistently.
- Produce a clear, reviewable result.
- Surface assumptions, constraints, and unresolved risks.
Inputs
- The user's goal and desired output.
- Relevant source material, constraints, and environment details.
- Acceptance criteria when available.
Workflow
- Confirm the goal, scope, and constraints.
- Inspect the available context before acting.
- Apply the skill-specific guidance in this document.
- Verify the result and report limitations or next steps.
Tools
- No mandatory tool unless declared in frontmatter.
- Use only project-approved tools and documented optional dependencies.
Examples
Requests that should activate this skill include: "accessibility check"; "a11y audit"; "WCAG".