# Accessibility Compliance > Use when implementing or reviewing accessibility - WCAG compliance, screen reader support, keyboard navigation, a11y testing - Skill: `kienbui1995/accessibility-compliance` (Agent Skill) - Install (CLI): `npx skillmds@latest add kienbui1995/accessibility-compliance` - Raw SKILL.md: https://api.skillmd.com/api/skills/kienbui1995/accessibility-compliance/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: kienbui1995 (https://skillmd.com/u/kienbui1995) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/kienbui1995/accessibility-compliance --- # Accessibility Compliance ## Overview Accessibility isn't optional — it's a legal requirement in many jurisdictions and affects ~15% of users. Build it in from the start, not as an afterthought. ## When to Use - Building new UI components - Reviewing existing interfaces for a11y - Fixing accessibility audit findings - Setting up automated a11y testing ## WCAG 2.1 Quick Reference (Level AA) ### Perceivable - **Color contrast** — 4.5:1 for normal text, 3:1 for large text - **Alt text** — all images have descriptive alt (or `alt=""` for decorative) - **Captions** — video has captions, audio has transcripts - **Don't rely on color alone** — use icons, patterns, or text too ### Operable - **Keyboard navigable** — all interactive elements reachable via Tab - **Focus visible** — clear focus indicator (never `outline: none` without replacement) - **Skip links** — "Skip to main content" link at top - **No keyboard traps** — user can always Tab away from any element ### Understandable - **Labels** — every form input has a visible `