a11yaudit

Audit web interfaces for accessibility barriers across 21-phase WCAG workflows.

10|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/agentik-os/OmegaOS --skill a11yaudit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11yaudit
Source: https://github.com/agentik-os/OmegaOS/tree/main/skills/audits/a11yaudit
Command: npx skills add https://github.com/agentik-os/OmegaOS --skill a11yaudit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forensic accessibility audit identifies and documents accessibility barriers across products, supporting teams in achieving WCAG 2.1 AA compliance through a rigorous, phase-based methodology.

Core Features & Use Cases

  • 21-phase audit workflow covering keyboard navigation, screen reader compatibility, ARIA semantics, heading structure, color contrast, focus management, and skip navigation to uncover hard-to-find accessibility issues.
  • Automated and manual testing fusion: automated checks through tooling plus expert forensic review to falsify optimistic tool results.
  • Real-world remediation planning: generates a fix plan and re-audit cycle to close gaps and verify improvements.
  • Use case: a new product feature is released; run a11yaudit to surface accessibility blockers and generate actionable remediation steps for your team.

Quick Start

Run the a11yaudit against your project to initiate a comprehensive accessibility-forensics workflow and generate actionable reports.

Frequently Asked Questions about a11yaudit

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

FAQPage Schema
How do I perform a WCAG accessibility audit on a single-page application?

A WCAG accessibility audit for SPAs evaluates routes across a 21-phase workflow covering keyboard navigation, screen reader compatibility, ARIA semantics, and focus management to identify barriers. The process fuses automated checks with expert forensic review to falsify optimistic tool results.

What is forensic accessibility auditing and how does it differ from automated scanning?

Forensic accessibility auditing combines automated tooling with expert manual review to expose hard-to-find barriers that automated scanners miss. It applies a rigorous 21-phase methodology across keyboard, ARIA, contrast, and screen reader tests to verify WCAG 2.1 AA compliance.

Can I generate an accessibility fix plan and re-audit cycle for my team?

Yes, the audit generates structured fix plans and re-audit cycles to close accessibility gaps and verify improvements. It produces structured reports, verdicts, and remediation steps suitable for both automated processing and human review.

Does the audit cover keyboard navigation and screen reader testing for WCAG 2.1 AA compliance?

Yes, the audit covers keyboard navigation, screen reader compatibility, ARIA conformance, heading structure, color contrast, focus management, and skip navigation across 21 phases to support WCAG 2.1 AA compliance for both static pages and SPA routes.

What are the limitations of automated accessibility checkers for finding ARIA barriers?

Automated accessibility checkers often produce optimistic results and miss complex ARIA, focus management, and screen reader barriers. A forensic audit falsifies these results by combining automated checks with manual expert review across 21 phases.