swarm-a11y-agent

Audit Next.js/React frontend code for WCAG AA accessibility compliance.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-a11y-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-a11y-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-a11y-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-a11y-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool provides a read-only audit of gnubok front-end code to identify WCAG AA accessibility issues, helping teams ensure keyboard navigability, visible focus, proper semantic HTML, and screen-reader compatibility without writing or altering code.

Core Features & Use Cases

  • Scan frontend files for WCAG AA compliance, including text and UI contrast, keyboard focus, focus rings, and aria-labels on icon-only controls.
  • Detect common accessibility problems across app/pages, components, and global styles, and produce actionable findings for developers and design teams.
  • Use cases include pre-release accessibility sweeps, ongoing code reviews, and compliance verification during UI iterations.

Quick Start

Run the swarm-a11y-agent to sweep the frontend and generate an accessibility findings report for WCAG AA issues.

Frequently Asked Questions about swarm-a11y-agent

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

FAQPage Schema
How do I audit my Next.js React codebase for WCAG AA accessibility compliance?

A WCAG AA accessibility audit of Next.js and React codebases scans app and component tsx files alongside global CSS to detect keyboard navigation, focus ring, color contrast, aria-label, and semantic HTML issues.

What is a read-only accessibility audit and how does it check frontend code?

A read-only accessibility audit evaluates frontend code without altering it, validating keyboard operability, visible focus indicators, screen-reader compatibility, and reduce-motion respect to identify WCAG 2.1 AA violations.

Does this accessibility checker detect color-only state indicators and contrast issues?

Yes, this accessibility checker detects color-only state indicators and validates text and UI color contrast against WCAG AA standards, ensuring information is not conveyed by color alone.

How do I verify keyboard navigation and focus rings in a React application?

Verifying keyboard navigation and focus rings in a React application involves scanning component tsx files to validate keyboard operability and ensure visible focus indicators are present on interactive elements.

Can I use this to check aria-labels on icon-only controls during a pre-release sweep?

Yes, you can check aria-labels on icon-only controls during pre-release accessibility sweeps to generate actionable findings for developers and design teams without modifying the codebase.

What are the limitations of running a static WCAG AA audit on frontend components?

A limitation of running a static WCAG AA audit is its read-only nature, meaning it cannot fix code, and its focus on tsx and CSS files may miss runtime DOM mutations or dynamic accessibility behaviors.