accessibility-audit

Audit design files and UI descriptions for WCAG 2.2 AAA, Section 508, and ARIA APG compliance.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessibility-audit-lord-vinayak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/accessibility-audit_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessibility-audit-lord-vinayak

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies accessibility issues in designs, Figma files, screenshots, or UI descriptions, ensuring compliance with WCAG and Section 508 standards.

Core Features & Use Cases

  • Design Layer Audit: Detects visual, layout, interactive, content, and mobile-specific accessibility issues.
  • Standards Coverage: Audits against WCAG 2.2 AAA, Section 508, and ARIA Authoring Practices Guide (APG).
  • Use Case: When a user needs to ensure their design is accessible before handoff or launch, they can use this Skill to conduct a thorough review.

Quick Start

Run the accessibility-audit skill on the provided Figma file to identify accessibility issues.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I check my Figma designs for WCAG 2.2 AAA compliance?

You can audit Figma designs for WCAG 2.2 AAA compliance by running an accessibility audit on static design files and UI annotations. This process identifies visual, layout, and interactive accessibility issues before handoff.

What is included in a comprehensive design accessibility audit?

A comprehensive design accessibility audit assesses visual, layout, interactive, content, and mobile-specific UI elements. It checks for compliance against WCAG 2.2 AAA, Section 508, and ARIA Authoring Practices Guide standards.

Can I use automated accessibility audits on UI descriptions without a Figma file?

Yes, automated accessibility audits can process static design files, screenshots, or UI descriptions directly. Providing clear UI descriptions and annotations allows the audit to identify Section 508 and WCAG issues accurately.

Does this accessibility audit check ARIA APG and Section 508 standards?

Yes, the accessibility audit evaluates designs against the ARIA Authoring Practices Guide and Section 508 standards. It specifically reports interactive issues and components that fail to meet these ARIA and Section 508 compliance requirements.

What are the limitations of auditing accessibility on static design files?

Auditing static design files requires clear UI annotations to accurately assess interactive and dynamic states. Without proper annotations, automated analysis may miss complex ARIA implementation issues or real-time mobile-specific accessibility behaviors.