auditing-accessibility-compliance

Audit developer documentation websites for WCAG 2.1 AA accessibility compliance.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/musher-dev/bundles --skill auditing-accessibility-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditing-accessibility-compliance
Source: https://github.com/musher-dev/bundles/tree/main/developer-docs-authoring/skills/auditing-accessibility-compliance
Command: npx skills add https://github.com/musher-dev/bundles --skill auditing-accessibility-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the auditing of developer documentation websites to ensure they meet WCAG 2.1 AA accessibility standards, identifying issues related to keyboard navigation, screen reader compatibility, color contrast, ARIA attributes, and more.

Core Features & Use Cases

  • WCAG AA Auditing: Evaluates documentation against specific WCAG 2.1 AA criteria relevant to web content.
  • Component Checks: Assesses accessibility of interactive elements like navigation, search, code blocks, and forms.
  • Use Case: When preparing to launch a new developer portal, use this skill to perform a comprehensive accessibility audit, ensuring compliance and a better user experience for all.

Quick Start

Run an accessibility audit on the provided documentation URL.

Frequently Asked Questions about auditing-accessibility-compliance

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

FAQPage Schema
How do I audit my developer documentation for WCAG AA compliance?

You can audit documentation for WCAG AA compliance by analyzing keyboard navigation, screen reader compatibility, color contrast, and ARIA attributes against WCAG 2.1 AA accessibility standards to identify and resolve compliance issues.

What accessibility checks are needed for developer documentation websites?

Accessibility checks for developer documentation include evaluating keyboard navigation, screen reader compatibility, color contrast, ARIA attributes, and interactive components like search and code blocks to ensure they meet WCAG 2.1 AA criteria.

How do I check keyboard navigation and screen reader compatibility in docs?

You can check keyboard navigation and screen reader compatibility by analyzing documentation structure and content, evaluating interactive elements like navigation, search, and forms to ensure they meet WCAG 2.1 AA accessibility standards.

Can I use an automated audit for WCAG 2.1 AA documentation compliance?

Automated WCAG 2.1 AA documentation compliance auditing is supported by reading, searching, and analyzing documentation content and structure to evaluate interactive elements and identify accessibility issues.

Does this accessibility audit check ARIA attributes and color contrast?

This accessibility audit checks ARIA attributes and color contrast along with keyboard navigation and screen reader compatibility, evaluating documentation content against WCAG 2.1 AA accessibility standards.

What components are evaluated during a documentation accessibility audit?

Components evaluated during a documentation accessibility audit include interactive elements like navigation, search, code blocks, and forms, assessed for keyboard navigation and screen reader compatibility against WCAG 2.1 AA criteria.