a11y-audit

Audit web interfaces for WCAG compliance gaps with structured findings.

453|34|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/josstei/maestro-orchestrate --skill a11y-audit-josstei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/josstei/maestro-orchestrate/tree/main/plugins/maestro/skills/a11y-audit
Command: npx skills add https://github.com/josstei/maestro-orchestrate --skill a11y-audit-josstei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking web applications for accessibility gaps that exclude users with disabilities is time-consuming, error-prone, and risks non-compliance with legal accessibility standards.

Core Features & Use Cases

  • WCAG Conformance Checking: Validate UI against WCAG A, AA, or AAA standards.
  • Comprehensive Accessibility Testing: Audit ARIA usage, keyboard navigation, focus management, color contrast, and screen reader compatibility.
  • Structured Findings Reporting: Get results with WCAG criterion references, severity levels, user impact, and actionable remediation code patterns. Use Case: Before launching a new customer-facing web portal, use this Skill to identify and fix accessibility issues to ensure all users can access your service and meet regulatory requirements.

Quick Start

Use the a11y-audit skill to run a WCAG AA accessibility audit on the public-facing product pages of the e-commerce site.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema
How do I audit my web application for WCAG compliance and screen reader compatibility?

WCAG accessibility audits identify compliance gaps in web user interfaces by validating ARIA implementation, keyboard navigation, focus management, color contrast, and screen reader compatibility against WCAG A, AA, or AAA standards.

What is the best way to check ARIA implementation and keyboard navigation for accessibility?

The best way to check ARIA implementation and keyboard navigation is through structured accessibility testing that validates focus management and screen reader compatibility. This reveals WCAG compliance gaps with severity ratings and actionable remediation patterns for inclusive design.

Does this accessibility audit provide actionable remediation code patterns for WCAG violations?

Yes, the accessibility audit delivers findings with WCAG criterion references, severity ratings, user impact assessments, and actionable remediation code patterns. This structured reporting ensures developers can directly fix keyboard navigation and ARIA implementation issues.

Can I test color contrast and focus management against WCAG AA standards?

Yes, you can validate color contrast and focus management against WCAG A, AA, or AAA standards. The audit checks these web UI elements to ensure regulatory compliance and produce structured findings with severity levels for prioritized remediation.

What level of WCAG conformance checking do I need for a customer-facing web portal?

For a customer-facing web portal, WCAG AA conformance checking is typically required to meet regulatory accessibility standards. This level validates ARIA usage, color contrast, and screen reader compatibility to ensure all users can access your service.