Accessibility Compliance

From the author

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.

— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to building inclusive digital experiences. It covers WCAG 2.2 compliance, ARIA patterns, keyboard navigation, and mobile accessibility. It emphasizes semantic HTML, proper focus management, and assistive technology support to ensure applications are perceivable, operable, understandable, and robust for all users.

What it does

Provides patterns for WCAG 2.2 compliant UI components like buttons, modals, and tabs.
Explains the correct usage of ARIA roles, states, and properties.
Outlines requirements for keyboard navigation and focus management.
Details mobile accessibility standards including touch target sizing and gesture support.
Offers a checklist for WCAG 2.2 success criteria.
Suggests manual and automated testing tools for accessibility audits.

When to use it

When designing or developing new web components that require accessibility compliance.
When auditing an existing application for WCAG 2.2 violations.
When implementing complex interactive widgets like accordions or dialogs.
When optimizing interfaces for screen readers and keyboard-only users.

Advantages

Promotes inclusive design by prioritizing semantic HTML.
Reduces common accessibility pitfalls like keyboard traps and missing labels.
Provides ready-to-use code patterns for accessible UI elements.
Ensures compliance with modern accessibility standards.

Usage examples

“How do I create an accessible modal dialog?”: The skill provides a pattern using focus trapping, Escape key handling, and proper ARIA labeling to ensure the modal is fully accessible to screen readers and keyboard users.
“What are the requirements for mobile touch targets?”: The skill specifies a minimum touch target size of 44x44dp to ensure ease of interaction for all users on mobile devices.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/wshobson/accessibility-compliance/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip accessibility-compliance.zip -d .agents/skills

Documentation by Seth Hobson

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

Use Semantic HTML: Prefer native elements over ARIA when possible
Test with Real Users: Include people with disabilities in user testing
Keyboard First: Design interactions to work without a mouse
Don't Disable Focus Styles: Style them, don't remove them
Provide Text Alternatives: All non-text content needs descriptions
Support Zoom: Content should work at 200% zoom
Announce Changes: Use live regions for dynamic content
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)

Files

ATTRIBUTION.mdAdded by AutoGineer990 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md2.3 KiB
references/aria-patterns.md12.9 KiB
references/details.md9.4 KiB
references/mobile-accessibility.md12.8 KiB
references/wcag-guidelines.md13.9 KiB

SKILL.md