agentic-a11y

Automate multi-agent accessibility audits across codebases with WCAG 2.2 AA guidance.

92|9|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Ovid/paad --skill agentic-a11y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-a11y
Source: https://github.com/Ovid/paad/tree/main/plugins/paad/skills/agentic-a11y
Command: npx skills add https://github.com/Ovid/paad --skill agentic-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility audits across codebases are labor-intensive and error-prone. This Skill automates multi-agent accessibility assessments to identify barriers across web, mobile, desktop, and CLI platforms, delivering a comprehensive, actionable report.

Core Features & Use Cases

  • Multi-agent audit that dispatches specialists for screen readers, color/contrast, keyboard/motor, cognitive/learning, and multimedia accessibility.
  • Phase-driven workflow: preflight checks, reconnaissance, parallel specialist audits, verification, and a final reviewed report.
  • Produces WCAG 2.2 AA-aligned findings mapped to platform guidelines with concrete fixes and a shareable report.

Quick Start

Run the audit with a11y skill: /paad:agentic-a11y to scan the repository; you can scope to a path like /paad:agentic-a11y src/components/ to limit the audit.

Frequently Asked Questions about agentic-a11y

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

FAQPage Schema
How do I automate a WCAG 2.2 AA accessibility audit across my codebase?

Automate a WCAG 2.2 AA accessibility audit using a multi-agent approach that dispatches specialists for screen readers, contrast, and motor accessibility across platforms to deliver an actionable final report.

Does multi-agent accessibility auditing work for mobile and desktop platforms?

Multi-agent accessibility auditing works across web, iOS, Android, desktop, CLI, and game platforms, applying platform-specific references to identify barriers and verify compliance.

How do I scope an accessibility audit to a specific directory in my repository?

Scope an accessibility audit to a specific directory by passing the target path like src/components/ as an argument, limiting the multi-agent investigation and reconnaissance to that location.

What is the best way to identify screen reader and cognitive accessibility barriers in code?

Identify screen reader and cognitive barriers using a multi-agent workflow that runs parallel specialist assessments, verifying findings against WCAG 2.2 AA guidelines for concrete fixes.

How does a multi-agent accessibility audit workflow execute its investigation phases?

A multi-agent accessibility audit executes through phase-driven workflows including preflight checks, reconnaissance, parallel specialist audits, and verification before generating a reviewed report.

What limitations exist when auditing game and CLI platforms for WCAG 2.2 compliance?

Auditing game and CLI platforms for WCAG 2.2 compliance requires platform-specific references and specialist agents, though complex interactive barriers may need manual verification beyond automated reconnaissance.