accessibility-audit

Audit user interfaces for WCAG compliance and generate remediation reports.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/radenadri/skills-alena --skill accessibility-audit-radenadri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/radenadri/skills-alena/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/radenadri/skills-alena --skill accessibility-audit-radenadri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps in user interfaces prevent inclusive experiences and can violate WCAG requirements. This Skill helps teams identify issues that block keyboard navigation, screen readers, and color-contrast accessibility, enabling remediation before launch.

Core Features & Use Cases

  • Comprehensive WCAG-focused accessibility audits across web UIs and component libraries.
  • Checks for keyboard navigation, focus management, screen reader compatibility, semantic HTML, and ARIA usage.
  • Generates actionable remediation guidance and a reproducible accessibility report for teams.

Quick Start

Run a full accessibility audit on your UI to identify keyboard navigation, screen reader, and color-contrast issues and generate a remediation plan.

Frequently Asked Questions about accessibility-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?

A WCAG accessibility audit evaluates keyboard navigation, screen reader compatibility, ARIA semantics, color contrast, and form accessibility across web interfaces. It identifies user interface accessibility gaps and generates a structured report with actionable remediation guidance for frontend applications and component libraries.

What does an accessibility audit check for in a component library?

An accessibility audit checks a component library for keyboard focus management, semantic HTML structure, correct ARIA usage, and accessible color contrast. It documents these accessibility gaps across all UI modules to ensure inclusive experiences and WCAG compliance before launch.

Can I use this to test keyboard navigation and screen reader compatibility?

Yes, this audit specifically tests keyboard navigation and screen reader compatibility. It evaluates keyboard focus management and screen reader compatibility, identifying accessibility gaps that block inclusive user experiences and violate WCAG requirements across web dashboards and component libraries.

What is the best way to document accessibility gaps for remediation?

The best way to document accessibility gaps for remediation is generating a reproducible accessibility report with a structured audit checklist. This report provides actionable guidance on fixing keyboard navigation, screen reader, and color-contrast issues for development teams.

Does an accessibility audit cover ARIA semantics and form accessibility?

Yes, an accessibility audit covers ARIA semantics and form accessibility. It checks for correct ARIA usage and form accessibility across frontend applications, web dashboards, and component libraries to identify and document gaps blocking WCAG compliance.

Why does my UI fail keyboard focus management during an accessibility audit?

Your UI fails keyboard focus management during an accessibility audit because it lacks semantic HTML or proper ARIA usage for keyboard navigation. The audit identifies these specific accessibility gaps and provides actionable remediation guidance to ensure WCAG compliance.