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

Accessibility Compliance

  • 11.5k installs
  • 38.3k repo stars
  • Updated July 22, 2026
  • wshobson/agents

How to build interfaces that meet WCAG 2.2 standards and work with assistive technologies like screen readers.

About

This skill teaches WCAG 2.2 Level AA/AAA compliance implementation for inclusive user interfaces. Covers semantic HTML, ARIA patterns, keyboard navigation, focus management, form accessibility, and mobile accessibility (VoiceOver, TalkBack). Developers use it when auditing accessibility violations, implementing screen reader support, building keyboard-navigable components, and ensuring compliance. Key workflows include testing with automated tools (axe, Lighthouse), manual testing with assistive technologies, and fixing common issues like missing alt text, poor contrast, keyboard traps, and unfocused form labels.

  • Semantic HTML-first approach with ARIA patterns for dynamic content
  • Keyboard navigation and focus management (no traps, respects tab order)
  • Mobile accessibility for iOS VoiceOver and Android TalkBack
  • WCAG 2.2 Level AA/AAA audit and violation fixes
  • Testing via axe DevTools, WAVE, Lighthouse, and real assistive tech (NVDA, JAWS)

Accessibility Compliance by the numbers

  • 11,454 all-time installs (skills.sh)
  • +215 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #47 of 2,277 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

accessibility-compliance capabilities & compatibility

Capabilities
audit accessibility violations with wcag 2.2 sta · implement semantic html and aria patterns · build keyboard navigation and focus management · create accessible forms with proper labeling · support mobile accessibility (voiceover, talkbac · test with automated and manual assistive technol
Use cases
ui design · web design · frontend · code review
Platforms
macOS · Windows · Linux
Runs
Runs locally
npx skills add https://github.com/wshobson/agents --skill accessibility-compliance

Add your badge

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

Listed on Skillselion
Installs11.5k
repo stars38.3k
Security audit3 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

What it does

Implement WCAG 2.2 compliant interfaces with screen reader support, keyboard navigation, and inclusive design patterns.

Who is it for?

Building customer-facing products, public-facing content sites, enterprise applications, mobile apps, and any product requiring legal accessibility compliance.

Skip if: Internal tools with no external users, non-interactive content, or projects with zero accessibility requirements.

When should I use this skill?

Auditing accessibility violations, implementing ARIA, building screen reader support, adding keyboard navigation, conducting compliance reviews.

What you get

Developers produce accessible interfaces that pass WCAG 2.2 audits, support keyboard and screen reader navigation, and include users with disabilities.

  • accessible component markup
  • ARIA attribute patterns
  • keyboard navigation implementation

By the numbers

  • WCAG 2.2 Level AA/AAA compliance standards
  • 8 core best practices documented (semantic HTML, keyboard first, focus styles, text alternatives, zoom support, live reg

Files

SKILL.mdMarkdownGitHub ↗

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)

Related skills

How it compares

Use accessibility-compliance for hands-on WCAG implementation and ARIA patterns, not for generic UI styling or color palette selection alone.

FAQ

When should I use ARIA vs semantic HTML?

Prefer native semantic elements (button, nav, main) over ARIA. Use ARIA only for dynamic content updates and custom components (live regions, roles when semantic HTML insufficient).

What are the most common accessibility failures?

Missing alt text on images, poor color contrast, keyboard traps, missing form labels, auto-playing media, inaccessible custom controls, and missing skip links.

How do I test accessibility without hiring auditors?

Use automated tools (axe DevTools, Lighthouse, WAVE), then manually test with free assistive tech: VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android).

Is Accessibility Compliance safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

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

unsubscribe anytime.