accessibility-audit

Name: accessibility-audit
Availability: InStock
Author: CivicActions

Audit web pages and components for WCAG 2.1 AA and Section 508 compliance.

2|Updated May 24, 2026

Search Tags:#accessibility #a11y #frontend #audit #compliance #wcag

Ready to run

npx skills add https://github.com/CivicActions/ai-runbook-jh --skill accessibility-audit-civicactions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill accessibility-audit-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the guesswork from accessibility compliance by providing a structured, repeatable audit process that ensures digital products meet WCAG 2.1 AA and Section 508 standards.

Core Features & Use Cases

Comprehensive Auditing: Performs both live browser inspection and static markup analysis to identify common accessibility barriers.
Context-Aware Reporting: Generates findings mapped to specific project contracts, including impact levels and priority schemes.
Use Case: Use this skill when reviewing a new component or page template to catch missing ARIA labels, color contrast issues, or keyboard navigation traps before they reach production.

Quick Start

Invoke the accessibility-audit skill on the current page or component to generate a prioritized list of compliance findings and remediation steps.

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 page for WCAG 2.1 AA compliance?▼

To audit web pages for WCAG 2.1 AA compliance, this skill performs automated static markup analysis and live browser inspection of DOM elements to identify accessibility barriers. It generates prioritized remediation steps mapped to project-specific impact levels.

What's the best way to check Section 508 compliance in front-end development?▼

Checking Section 508 compliance in front-end workflows requires a structured audit process combining live browser inspection and static analysis. This skill identifies missing ARIA labels, color contrast issues, and keyboard navigation traps before production.

Does this accessibility audit work with custom design system styling rules?▼

Yes, the accessibility audit works with custom design system styling rules by ensuring adherence to project-specific contracts during the inspection process. It applies impact-based prioritization to findings generated from static markup and live DOM element analysis.

Can I catch keyboard navigation traps and ARIA label issues before production?▼

You can catch missing ARIA labels, color contrast issues, and keyboard navigation traps before production by invoking this skill on new components or page templates. It provides a repeatable audit process ensuring digital products meet accessibility standards.

How are accessibility findings prioritized for remediation?▼

Accessibility findings are prioritized for remediation using impact-based prioritization schemes mapped to specific project contracts. The audit generates a structured list of compliance findings and remediation steps based on WCAG 2.1 AA and Section 508 standards.