Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Accessibility Compliance

  • 434 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

accessibility-compliance is an aj-geddes/useful-ai-prompts agent skill that audits and implements WCAG 2.1/2.2 accessibility patterns for developers shipping inclusive web UIs.

About

accessibility-compliance is an aj-geddes/useful-ai-prompts Claude Code skill from a library of 260+ skills and 488+ validated prompts. It implements WCAG 2.1/2.2 AA and AAA patterns including semantic HTML, ARIA usage, keyboard navigation, focus management, screen reader announcements, and color contrast validation at a 4.5:1 minimum for normal text. Six reference guides cover semantic HTML with ARIA, React accessible components, keyboard handlers, contrast validators, screen reader live regions, and focus trapping. Quick-start examples contrast non-semantic div buttons with proper button elements, tabindex handling, and labeled form fields. The skill supports audits for NVDA, JAWS, and VoiceOver compatibility and ADA or Section 508 alignment. Developers reach for accessibility-compliance before release or during pre-ship design review when components need measurable a11y remediation rather than ad-hoc fixes.

  • WCAG-oriented audit prompt patterns
  • Keyboard and focus-order checks
  • Color contrast and readable text rules
  • ARIA labels and semantic HTML review
  • Remediation suggestions for common violations

Accessibility Compliance by the numbers

  • 434 all-time installs (skills.sh)
  • Ranked #657 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill accessibility-compliance

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs434
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you audit web components for WCAG compliance?

Audit pages and components for WCAG-oriented accessibility issues—contrast, keyboard paths, labels, focus order—before release or during pre-ship design review.

Who is it for?

Frontend developers preparing public-facing React or HTML apps for WCAG 2.1/2.2 AA audits and screen reader compatibility.

Skip if: Native mobile-only apps without web markup or teams that only need automated Lighthouse runs without component-level remediation patterns.

When should I use this skill?

Pages or components need pre-ship accessibility review for contrast, keyboard navigation, labels, or focus management.

What you get

Remediation checklists, accessible component code snippets, contrast fixes, and keyboard navigation handlers

  • Accessible component snippets
  • Contrast remediation guidance
  • Keyboard navigation handlers

By the numbers

  • Includes 6 reference guides in the references/ directory
  • Targets WCAG 2.1/2.2 with 4.5:1 minimum color contrast for normal text
  • From useful-ai-prompts library with 260+ Claude Code skills

Files

SKILL.mdMarkdownGitHub ↗

Accessibility Compliance

Table of Contents

Overview

Implement comprehensive accessibility features following WCAG guidelines to ensure your application is usable by everyone, including people with disabilities.

When to Use

  • Building public-facing web applications
  • Ensuring WCAG 2.1/2.2 AA or AAA compliance
  • Supporting screen readers (NVDA, JAWS, VoiceOver)
  • Implementing keyboard-only navigation
  • Meeting ADA, Section 508, or similar regulations
  • Improving SEO and overall user experience
  • Conducting accessibility audits

Quick Start

Minimal working example:

<!-- Bad: Non-semantic markup -->
<div class="button" onclick="submit()">Submit</div>

<!-- Good: Semantic HTML -->
<button type="submit" aria-label="Submit form">Submit</button>

<!-- Custom components with proper ARIA -->
<div
  role="button"
  tabindex="0"
  aria-pressed="false"
  onclick="toggle()"
  onkeydown="handleKeyPress(event)"
>
  Toggle Feature
</div>

<!-- Form with proper labels and error handling -->
<form>
  <label for="email">Email Address</label>
  <input
    id="email"
    type="email"
    name="email"
    aria-required="true"
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Semantic HTML with ARIASemantic HTML with ARIA
React Component with AccessibilityReact Component with Accessibility
Keyboard Navigation HandlerKeyboard Navigation Handler
Color Contrast ValidatorColor Contrast Validator
Screen Reader AnnouncementsScreen Reader Announcements
Focus ManagementFocus Management

Best Practices

✅ DO

  • Use semantic HTML elements
  • Provide text alternatives for images
  • Ensure sufficient color contrast (4.5:1 minimum)
  • Support keyboard navigation
  • Implement focus management
  • Test with screen readers
  • Use ARIA attributes correctly
  • Provide skip links
  • Make forms accessible with labels
  • Support text resizing up to 200%

❌ DON'T

  • Rely solely on color to convey information
  • Remove focus indicators
  • Use only mouse/touch interactions
  • Auto-play media without controls
  • Create keyboard traps
  • Use positive tabindex values
  • Override user preferences
  • Hide content only visually that should be hidden from screen readers

Related skills

How it compares

Pick accessibility-compliance over generic lint rules when you need component-level WCAG remediation patterns and screen reader workflows, not just axe CI gates.

FAQ

Which WCAG versions does accessibility-compliance cover?

accessibility-compliance implements WCAG 2.1 and WCAG 2.2 patterns targeting AA compliance with guidance toward AAA, including contrast, keyboard access, and screen reader support.

How many reference guides ship with accessibility-compliance?

accessibility-compliance includes 6 reference guides covering semantic HTML with ARIA, React components, keyboard navigation, color contrast, screen reader announcements, and focus management.

When should accessibility-compliance run in a release cycle?

accessibility-compliance fits pre-ship design review and release audits when public-facing pages need WCAG remediation for contrast, labels, keyboard paths, and focus order.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.