accessibility

Audit web and mobile interfaces for WCAG 2.2 AA accessibility violations.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill accessibility-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/mahg-es/araya/tree/main/skills/accessibility
Command: npx skills add https://github.com/mahg-es/araya --skill accessibility-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inaccessible applications exclude 15-20% of users and may violate legal requirements. This skill audits for accessibility violations and produces fixes that make applications perceivable, operable, understandable, and robust for all users.

Core Features & Use Cases

  • Accessibility auditing against WCAG 2.2 AA
  • ARIA role and semantic HTML recommendations
  • Remediation guidance and checklists for developers

Quick Start

Run an accessibility audit on the target app and apply fixes to achieve WCAG 2.2 AA conformance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my web app for WCAG 2.2 AA compliance?

To audit web accessibility for WCAG 2.2 AA compliance, evaluate semantic HTML, ARIA usage, keyboard navigation, color contrast, and focus management to identify violations across user interfaces and generate remediation checklists.

What is the best way to remediate ARIA roles and semantic HTML for accessibility?

The best way to remediate ARIA roles and semantic HTML is to audit existing markup against WCAG 2.2 AA standards, then apply targeted fixes to ensure elements are perceivable, operable, and robust for all users.

Does WCAG 2.2 AA accessibility testing cover both web and mobile interfaces?

Yes, WCAG 2.2 AA accessibility testing covers both web and mobile interfaces, auditing interactive elements, focus management, and keyboard navigation to ensure usability across platforms for development and QA teams.

Why does keyboard navigation fail during web accessibility audits?

Keyboard navigation fails during web accessibility audits when focus management is improperly implemented, preventing operability. Remediation involves correcting ARIA roles and semantic HTML to restore logical focus order for users.