Accessibility Auditor

Audit user interfaces against WCAG 2.2 AA and generate remediation guidance.

Updated Apr 16, 2026

Search Tags:#accessibility #a11y #remediation #wcag #screen-reader #a11y-testing #assistive-technology

Ready to run

npx skills add https://github.com/jc180105/.opencode --skill accessibility-auditor-jc180105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Accessibility Auditor
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/testing-accessibility-auditor
Command: npx skills add https://github.com/jc180105/.opencode --skill accessibility-auditor-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility challenges hinder usable interfaces for people with disabilities. This Skill provides rigorous auditing against WCAG 2.2 AA, manual assistive technology testing, and actionable remediation guidance.

Core Features & Use Cases

Comprehensive WCAG Evaluation: Assess interfaces against WCAG 2.2 AA criteria, including focus management and reading order.
Assistive Technology Testing: Validate with screen readers, keyboard navigation, and cognitive accessibility considerations.
Remediation Guidance: Deliver actionable, WCAG-referenced fixes with code examples and recommended design changes.
Use Case: For a new web app, generate an accessibility report and prioritized remediation plan for developers and designers.

Quick Start

Audit a new product dashboard for WCAG 2.2 AA conformance and generate a remediation-ready accessibility report.

Frequently Asked Questions about Accessibility Auditor

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

FAQPage Schema

How do I audit a web interface for WCAG 2.2 AA compliance?▼

To audit a web interface for WCAG 2.2 AA compliance, evaluate product features and components against criteria like focus management and reading order, then validate using screen readers and keyboard navigation to identify issues.

What is the best way to test screen reader compatibility during UI development?▼

Testing screen reader compatibility involves manual assistive technology validation across your user interfaces, checking cognitive accessibility considerations, keyboard navigation, and reading order to ensure true accessibility.

How do I generate an accessibility remediation plan for developers?▼

An accessibility remediation plan is generated by auditing interfaces against WCAG 2.2 AA, identifying failures, and delivering actionable fixes with clear WCAG references, code examples, and recommended design changes for developers.

Can I assess cognitive accessibility and keyboard navigation for a new web app?▼

You can assess cognitive accessibility and keyboard navigation by performing manual assistive technology testing across your new web app's pages and components to ensure comprehensive coverage.

Why does my automated a11y testing miss focus management issues?▼

Automated a11y testing misses focus management issues because true validation requires manual assistive technology testing to verify reading order, keyboard navigation, and screen reader interactions against WCAG 2.2 AA criteria.

Does the Accessibility Auditor apply to individual UI components or entire product pages?▼

Accessibility auditing applies across individual UI components, entire product pages, and product features to ensure comprehensive coverage and assistive technology compatibility throughout the user interface.