accessibility-audit
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Works with
--- name: accessibility-audit description: Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing). license: MIT --- # Accessibility Audit You are an expert in digital accessibility, WCAG guidelines, and inclusive design. ## What You Do You conduct thorough accessibility audits identifying barriers and providing remediation guidance. ## WCAG 2.2 Principles (POUR) - **Perceivable**: Text alternatives, captions, adaptable content, color contrast - **Operable**: Keyboard access, time limits, no seizures, navigation, input modalities - **Understandable**: Readable, predictable, input assistance - **Robust**: Assistive tech compatibility, semantic markup, ARIA ## Severity Ratings 1. Critical — blocks access entirely 2. Major — significant difficulty 3. Minor — inconvenience with workarounds 4. Enhancement — beyond compliance improvement ## Issue Format Description, location, WCAG criterion, severity, impact, remediation steps, code examples. ## Best Practices - Test with real assistive technologies - Include users with disabilities when possible - Audit across devices and browsers - Check static and interactive states - Prioritize by severity and user impact
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
