a11y

Audit, remediate, and critique Volume's UI for WCAG 2.2 AA compliance.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill a11y-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/a11y
Command: npx skills add https://github.com/misty-step/volume --skill a11y-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps in Volume's Next.js UI hinder usability for users with disabilities. This skill provides a triad workflow to audit, remediate, and critique to achieve WCAG 2.2 AA compliance.

Core Features & Use Cases

  • End-to-end accessibility auditing across app routes, components, and paywalls.
  • Separate execution stages: audit (identify issues), remediate (fix issues), critique (verify fixes) to ensure parity across light, dark, and system themes.
  • Guidance for running and validating fixes with a structured, repeatable process.

Quick Start

Audit a11y on the app by running the provided workflow and review findings.

Frequently Asked Questions about a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Next.js UI for WCAG 2.2 AA compliance?

You audit Next.js UI for WCAG 2.2 AA compliance by running a structured workflow that evaluates routes, components, and paywalls. It identifies accessibility gaps across light, dark, and system themes to generate actionable findings.

What is the best way to fix keyboard navigation and focus management issues in a React app?

Fixing keyboard navigation and focus management issues is handled through a dedicated remediation stage. It guides you in enforcing accessible names, proper semantic HTML, and correct focus order to resolve the identified audit failures.

Can I verify if my UI accessibility fixes work across light and dark themes?

Yes, you verify UI accessibility fixes across light, dark, and system themes using the critique stage. It critiques the remediated UI to ensure parity and confirm WCAG 2.2 AA compliance is maintained throughout different theme configurations.

How do I ensure accessible names and proper error messaging in my web components?

Ensure accessible names and proper error messaging in web components by applying the remediation stage's guidelines. It enforces correct semantic HTML structure and accessible error messaging to meet WCAG 2.2 AA standards during the component fixing process.

Does this accessibility audit process support paywall screens and app routes?

Yes, the accessibility audit process supports paywall screens and app routes. It evaluates all app surfaces within the src/app and src/components directories, enabling comprehensive end-to-end evaluation of your entire application.