a11y-audit

Audit Loom-style applications for WCAG violations and ARIA usage.

2|Updated Apr 4, 2026

Search Tags:#accessibility #a11y #audit #wcag #keyboard #screen-reader #aria

Ready to run

npx skills add https://github.com/Nickalus12/Loom --skill a11y-audit-nickalus12

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/a11y-audit
Command: npx skills add https://github.com/Nickalus12/Loom --skill a11y-audit-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Loom-style accessibility audits to identify WCAG violations, ARIA misuse, keyboard navigation gaps, and screen reader issues.

Core Features & Use Cases

Automated WCAG checks: ARIA usage, role semantics, contrast, and focus management.
Comprehensive evaluation: keyboard navigation, screen reader compatibility, and semantic correctness.
Use Case: run audits across Loom-like apps to ensure accessibility in UI components and pages.

Quick Start

Define the audit scope or target files and run the audit against your Loom app.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema

How do I run an automated WCAG audit on my web app's UI components?▼

Automated WCAG audits analyze UI components by evaluating ARIA usage, role semantics, contrast, and focus management to identify accessibility violations. To run it, define the audit scope or target files and execute the audit against your application.

What is the best way to check keyboard navigation and screen-reader compatibility across my application?▼

Checking keyboard navigation and screen-reader compatibility requires a comprehensive evaluation of semantic correctness and focus management. Automated audits enforce checks for keyboard navigation patterns to ensure interactive elements are fully accessible.

Can I audit specific forms and navigation flows for ARIA misuse?▼

You can audit specific forms and navigation flows by defining the target files as your audit scope. The audit analyzes these UI components for ARIA misuse and WCAG violations to ensure screen-reader compatibility.

Does this accessibility audit evaluate color contrast and focus management issues?▼

This accessibility audit evaluates color contrast and focus management issues directly. It enforces automated checks for WCAG criteria, including contrast ratios and focus management, to identify visual and interactive accessibility violations.

How do I identify WCAG violations in a Loom-style application?▼

Identifying WCAG violations in a Loom-style application involves analyzing UI components, forms, and navigation for ARIA usage and semantic correctness. Automated audits enforce these checks across components to ensure keyboard accessibility and screen-reader compatibility.