skilld
All skills
wshobson avatar

/accessibility-compliance

@be57c0b
by Seth Hobsonwshobson/agents40k stars
4,281

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Ask your Agent

Use this Skill: https://skilld.dev/gh/wshobson/agents/accessibility-compliance

This session only. Nothing lands on disk.

SKILL.md

≈71 tokens always: the name and description. ≈523 when used: this file. ≈13k more on demand in 4 files.

Accessibility Compliance

Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.

When to Use This Skill

  • Implementing WCAG 2.2 Level AA or AAA compliance
  • Building screen reader accessible interfaces
  • Adding keyboard navigation to interactive components
  • Implementing focus management and focus trapping
  • Creating accessible forms with proper labeling
  • Supporting reduced motion and high contrast preferences
  • Building mobile accessibility features (iOS VoiceOver, Android TalkBack)
  • Conducting accessibility audits and fixing violations

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

  1. Use Semantic HTML: Prefer native elements over ARIA when possible
  2. Test with Real Users: Include people with disabilities in user testing
  3. Keyboard First: Design interactions to work without a mouse
  4. Don't Disable Focus Styles: Style them, don't remove them
  5. Provide Text Alternatives: All non-text content needs descriptions
  6. Support Zoom: Content should work at 200% zoom
  7. Announce Changes: Use live regions for dynamic content
  8. Respect Preferences: Honor prefers-reduced-motion and prefers-contrast

Common Issues

  • Missing alt text: Images without descriptions
  • Poor color contrast: Text hard to read against background
  • Keyboard traps: Focus stuck in component
  • Missing labels: Form inputs without associated labels
  • Auto-playing media: Content that plays without user initiation
  • Inaccessible custom controls: Recreating native functionality poorly
  • Missing skip links: No way to bypass repetitive content
  • Focus order issues: Tab order doesn't match visual order

Testing Tools

  • Automated: axe DevTools, WAVE, Lighthouse
  • Manual: VoiceOver (macOS/iOS), NVDA/JAWS (Windows), TalkBack (Android)
  • Simulators: NoCoffee (vision), Silktide (various disabilities)

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The accessibility-compliance skill is a comprehensive reference for implementing WCAG 2.2 standards. It provides valid code patterns and best practices for web and mobile accessibility without any malicious behavior.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    4 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at be57c0b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago

Topics

  • wcag
  • aria
  • screen-reader
  • accessibility
  • keyboard-navigation
  • inclusive-design
  • focus-management
  • mobile-accessibility
  • semantic-html

README badge

README badge for wshobson/agents/accessibility-compliance

What it does

Implements WCAG 2.2 Level AA/AAA compliance patterns for web interfaces, including semantic HTML, ARIA, keyboard navigation, screen reader support, and mobile accessibility (VoiceOver, TalkBack). Use for auditing accessibility violations, adding focus management, building accessible forms, and supporting assistive technologies.

Generated from the current SKILL.md.

Frequently asked

Does this skill cover WCAG 2.2 Level AAA compliance?
Yes. The skill covers Level AA and AAA compliance, though Level AA is the more common target for most applications.
What screen readers does this skill support?
The skill covers VoiceOver (macOS/iOS), NVDA and JAWS (Windows), and TalkBack (Android). It focuses on semantic HTML and ARIA patterns that work across these assistive technologies.
Does this skill include testing tools or just implementation guidance?
The skill provides implementation patterns and best practices. It references testing tools like axe DevTools, WAVE, and Lighthouse, but the focus is on building accessible interfaces and fixing common violations.
Can this skill help with keyboard navigation and focus management?
Yes. The skill explicitly covers keyboard navigation, focus management, focus trapping, and ensuring tab order matches visual order in interfaces.
Does this skill address mobile accessibility?
Yes. It includes patterns for iOS VoiceOver and Android TalkBack, as well as mobile-specific accessibility concerns like zoom support and touch targets.

Generated from the current SKILL.md. These answers refresh after source changes.