domains / families / software-engineering / accessibility

accessibility

combined

Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast". Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

When to use

Skill page

Conflict

The two skills cover the same domain but have distinct, non-overlapping material steps. The first skill (addyosmani) provides a specific 'Evidence-led audit workflow' involving Lighthouse/axe tools, accessibility-tree snapshots, and a re-run verification loop, which the second skill lacks. The second skill (LeoYeAI) provides a '5-Step Accessibility Process' with a semantic HTML decision tree, specific ARIA usage rules (Golden Rule), and a detailed React/TypeScript focus-trap implementation, which the first skill lacks. Additionally, they target different WCAG versions (2.2 vs 2.1). Combining them creates a complete skill that covers both the audit/verification process and the implementation patterns.