accessibility-audit

Audit WCAG 2.1 AA conformance and generate prioritized findings reports.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill accessibility-audit-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/accessibility-audit
Command: npx skills add https://github.com/AAbdulghany/fms --skill accessibility-audit-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps in web and app interfaces hinder usability and compliance. This skill identifies, prioritizes, and documents issues so teams can remediate effectively.

Core Features & Use Cases

  • Deep-dive WCAG 2.1 AA checks across content, controls, and interactions.
  • Generates a prioritized findings list with explicit fix instructions for developers and designers.
  • Use Case: before a product release, scan a web app to surface accessibility defects and remediation steps.

Quick Start

Run the accessibility-audit on your project to generate a prioritized findings report.

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 app for WCAG 2.1 AA conformance?

To audit web app interfaces for WCAG 2.1 AA conformance, run a structured scan against POUR principles to identify accessibility gaps across pages, controls, and content. This generates a prioritized findings report with explicit remediation steps for developers and designers.

What is the best way to find accessibility gaps before a product release?

The best way to find accessibility gaps before release is to perform a deep-dive WCAG 2.1 AA audit. This surfaces defects across interactions and content, generating a prioritized findings list with actionable fix instructions for immediate remediation.

Does the accessibility audit provide machine-readable reports for QA tracking?

Yes, the accessibility audit exports generated findings data in a machine-readable format. This allows QA and development teams to systematically track identified WCAG 2.1 AA conformance issues and integrate remediation steps into existing workflows.

Can I use this audit to check both web and mobile app interfaces?

Yes, you can use this audit to check both web and app interfaces. It performs deep-dive WCAG 2.1 AA checks across content, controls, and interactions to surface accessibility defects and provide explicit fix instructions for either platform.

How does a WCAG 2.1 AA audit identify and prioritize issues?

A WCAG 2.1 AA audit identifies issues by running a structured scan against POUR principles. It then prioritizes the findings into a report that includes explicit remediation steps, helping teams effectively fix accessibility gaps in their interfaces.

When do I need to run an accessibility audit during development?

You should run an accessibility audit during development, QA, or pre-release stages. Scanning your project against WCAG 2.1 AA criteria at these stages surfaces accessibility defects early, allowing time for remediation before the product reaches users.