Accessibility is not a polish pass. It is a product requirement that must survive design, implementation, and QA.
Context
Use this skill when UI work, interaction design, content structure, or acceptance criteria need explicit accessibility treatment. The goal is to make requirements concrete enough that implementation and review can verify them.
Inputs
- Current UI scope, flow, or requirement set
- Known assistive-technology expectations
- Existing design or component constraints
Process
Step 1: Identify the user-facing surface
List the screens, controls, content blocks, and interaction states affected by the change.
Step 2: Define the accessibility contract
Specify the expected behavior for:
- keyboard access
- focus order and visible focus
- semantic structure and labels
- contrast and status communication
- error handling and announcements
Step 3: Turn requirements into checks
Translate the contract into reviewable checks that implementation and QA can execute without guesswork.
Step 4: Record the remediation path
If gaps already exist, document the minimum remediation sequence and who owns each part.
Outputs
- accessibility-guidance -- the concrete accessibility contract, checks, and remediation notes for the affected surface
Quality Gate
- Affected UI surfaces are named explicitly
- Keyboard, semantics, feedback, and contrast expectations are documented
- Reviewers can verify the result without inventing extra rules
Anti-Patterns
- Accessibility as a final sweep -- waiting until the end guarantees rework.
- Checklist without scope -- generic standards are not enough if the affected UI is undefined.
- Visual-only acceptance -- a screen can look correct and still fail users badly.
Related Skills
- requirements-engineering -- captures accessibility requirements early
- feature-development -- implements the required behavior
- testing-strategy -- verifies accessibility checks
Distribution
- Public install surface:
skills/.curated - Canonical authoring source:
skills/cross-cutting/accessibility/SKILL.md - This package is exported for
npx skills add/updatecompatibility. - Packaging stability:
beta - Capability readiness:
beta