a11y-auditor

Audit web interfaces against WCAG 2.2 AA standards with assistive technologies.

2|Updated Feb 25, 2026

Search Tags:#inclusive design #accessibility #a11y #screen reader #keyboard navigation #wcag

Ready to run

npx skills add https://github.com/elihuvillaraus/skills --skill a11y-auditor-elihuvillaraus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y-auditor
Source: https://github.com/elihuvillaraus/skills/tree/main/a11y-auditor
Command: npx skills add https://github.com/elihuvillaraus/skills --skill a11y-auditor-elihuvillaraus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital products accessible to everyone, including people with disabilities, by identifying and rectifying accessibility barriers.

Core Features & Use Cases

WCAG Auditing: Evaluates interfaces against WCAG 2.2 AA standards, covering POUR principles.
Assistive Technology Testing: Verifies compatibility with screen readers, keyboard navigation, and other assistive technologies.
Actionable Remediation: Provides concrete, code-level guidance for fixing identified issues.
Use Case: Before launching a new web application feature, use this Skill to perform a comprehensive accessibility audit, ensuring it meets legal requirements and provides an inclusive user experience.

Quick Start

Run a full accessibility audit on the current project's main page.

Frequently Asked Questions about a11y-auditor

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

FAQPage Schema

How do I audit my web application for WCAG 2.2 AA compliance?▼

A WCAG 2.2 AA accessibility audit evaluates interfaces against POUR principles using assistive technologies like screen readers and keyboard-only navigation. It identifies barriers missed by automation and provides actionable, code-level remediation guidance for inclusive design.

How do I test custom components for screen reader compatibility?▼

Testing custom components for screen reader compatibility involves verifying dynamic content navigation and announcements using assistive technologies. This process catches accessibility issues in custom interfaces and generates concrete remediation steps to ensure inclusive design.

What is the best way to find keyboard navigation barriers in dynamic content?▼

Finding keyboard navigation barriers in dynamic content requires testing against WCAG 2.2 AA standards using keyboard-only navigation. This approach catches issues automation misses in custom components and delivers actionable code-level guidance to fix keyboard navigation.

Can I use automated testing tools instead of a manual accessibility audit?▼

Automated testing tools alone cannot replace a manual accessibility audit. Manual testing against WCAG 2.2 AA catches accessibility barriers missed by automation, particularly in custom components and dynamic content, providing actionable remediation guidance for inclusive design.

When do I need to perform an accessibility audit with assistive technologies?▼

You need an accessibility audit with assistive technologies before launching new web application features. Testing with screen readers and keyboard navigation ensures interfaces meet WCAG 2.2 AA legal requirements and provide an inclusive user experience for people with disabilities.