← ClaudeAtlas

accessibilitylisted

Accessibility (a11y) compliance checking with WCAG 2.1 validation
manastalukdar/ai-devstudio · ★ 1 · AI & Automation · score 75
Install: claude install-skill manastalukdar/ai-devstudio
# Accessibility (a11y) Compliance Checking I'll analyze your web application for accessibility issues, validate WCAG 2.1 compliance, check ARIA attributes, verify keyboard navigation, validate color contrast, and generate comprehensive accessibility reports. **Compliance Standards:** - WCAG 2.1 Level A (minimum compliance) - WCAG 2.1 Level AA (target standard) - WCAG 2.1 Level AAA (enhanced accessibility) - Section 508 (US federal requirements) - EN 301 549 (EU accessibility requirements) **Frameworks Supported:** - React (React Testing Library, jest-axe) - Vue.js (Vue Test Utils, vue-axe) - Angular (Angular testing utilities) - HTML/CSS (static analysis) - Next.js, Gatsby, Nuxt.js **Arguments:** `$ARGUMENTS` - optional: - URL to audit (defaults to http://localhost:3000) - WCAG level (A, AA, AAA - defaults to AA) - Focus area: --images, --forms, --keyboard, --contrast, --aria (for targeted analysis) <think> Accessibility ensures: - Usability for people with disabilities - Keyboard-only navigation support - Screen reader compatibility - Visual accessibility (contrast, font size) - Cognitive accessibility (clear language, structure) Common a11y issues: - Missing alt text on images - Insufficient color contrast - Missing ARIA labels - Non-semantic HTML - Keyboard navigation barriers - Missing form labels - Poor heading hierarchy </think> ## Phase 1: Framework & Tool Detection First, I'll detect your framework and set up accessibility testing tools: ```bash #!/bin/bash