Accessibility remediation
Prioritize barriers by user impact and verify repairs manually and with tooling.
Customize the recipe
0/1500 characters
Prompt preview
# Accessibility remediation Prioritize barriers by user impact and verify repairs manually and with tooling. ## Deliverable Prioritized findings, scoped patches and evidence per remediated barrier. ## Stack and visual direction - Recommended starting stack: Use the existing stack, browser tooling and the project's test commands. Capture before-and-after evidence. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Use this direction for any new or revised UI within the agreed patch scope. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance. Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually. - [axe-core](https://github.com/dequelabs/axe-core) (Repository) — Find programmatically detectable accessibility issues and verify manual checks separately. - [WCAG 2.2](https://www.w3.org/TR/WCAG22/) (Standard) — Use the relevant WCAG AA criteria for manual and automated web checks. ## Workflow 1. Audit the critical user journeys with axe, keyboard and a screen reader where available. Group repeated causes, fix the shared component where practical, and recheck the journey. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Repeat each reported task with keyboard only and verify focus is visible. - [ ] Re-run automated checks and document manual issues that need further work. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Capture a reproducible baseline, validate the changed flow afterward, and report evidence and any findings still open.
Recipe resources
Source, setup, and compatibility details.
Web Design Guidelines
Review frontend UI against usability and accessibility guidance.
Access to the current upstream guidelines for the skill's full review.
License · MIT
axe-core
Find programmatically detectable accessibility issues and verify manual checks separately.
License · MPL-2.0
WCAG 2.2
Use the relevant WCAG AA criteria for manual and automated web checks.
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI