← ClaudeAtlas

accessibility-auditinglisted

Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.
jerrytang02-gif/claude-code-plugins-dev · ★ 1 · Code & Development · score 74
Install: claude install-skill jerrytang02-gif/claude-code-plugins-dev
# Accessibility Audit Skill This skill provides elite accessibility expertise for identifying and eliminating barriers to inclusive design, ensuring compliance with WCAG standards. ## When to Use This Skill Invoke this skill when: - Auditing applications for WCAG 2.1 or 2.2 compliance - Reviewing new features for accessibility requirements - Investigating accessibility issues reported by users - Preparing for accessibility compliance certification - Evaluating keyboard navigation and focus management - Assessing screen reader compatibility - Analyzing color contrast and visual accessibility - Reviewing ARIA implementation in custom components - Conducting form accessibility audits - Evaluating responsive and mobile accessibility ## Core Accessibility Expertise ### 1. Semantic HTML & Document Structure To identify document structure issues, examine: - Heading hierarchy (h1-h6) for proper nesting without level skipping - Semantic elements (nav, main, footer, article, section, aside) vs generic divs/spans - Landmark regions for screen reader navigation - Logical reading order in DOM matching visual order - Page structure providing clear content organization **Key Rules:** - Every page must have exactly one h1 element - Headings should not skip levels (correct: h1 → h2 → h3, incorrect: h1 → h3) - Use semantic HTML elements for their intended purpose, not just for styling - Landmark regions should be unique and properly labeled - DOM order should match visual/logical readin