skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
laurigates/claude-plugins63 installs

accessibility-implementation

WCAG 2.1/2.2 compliance, ARIA patterns, keyboard nav, focus management, a11y testing. Use when implementing accessible components or user mentions WCAG/ARIA/screen readers.

How do I install this agent skill?

npx skills add https://github.com/laurigates/claude-plugins --skill accessibility-implementation
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides comprehensive technical guidance, code examples, and testing procedures for web accessibility compliance (WCAG 2.1/2.2 and ARIA). It utilizes standard industry-recognized testing tools and follows established web development best practices. No security threats or malicious patterns were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

Accessibility Implementation

Technical implementation of WCAG guidelines, ARIA patterns, and assistive technology support.

When to Use This Skill

Use this skill when...Use design-tokens instead when...
Implementing WCAG 2.1/2.2 success criteria in codeSetting up CSS custom properties or theme systems
Adding ARIA roles, states, or live regionsDefining semantic colour tokens used by themes
Wiring keyboard navigation, focus traps, or skip linksOrganizing primitive/semantic/component token tiers
Auditing components with axe-core, jest-axe, or PlaywrightImplementing light/dark mode token overrides

Core Expertise

  • WCAG Compliance: Implementing WCAG 2.1/2.2 success criteria in code
  • ARIA Patterns: Correct usage of roles, states, and properties
  • Keyboard Navigation: Focus management, key handlers, logical tab order
  • Screen Readers: Content structure, announcements, live regions
  • Testing: Automated and manual accessibility testing

WCAG Quick Reference

Level A (Must Have)

CriterionImplementation
1.1.1 Non-text Contentalt for images, labels for inputs
1.3.1 Info and RelationshipsSemantic HTML, ARIA relationships
2.1.1 KeyboardAll interactive elements keyboard accessible
2.4.1 Bypass BlocksSkip links, landmarks
4.1.2 Name, Role, ValueARIA labels, roles for custom widgets

Level AA (Should Have)

CriterionImplementation
1.4.3 Contrast (Minimum)4.5:1 text, 3:1 large text
1.4.11 Non-text Contrast3:1 for UI components
2.4.6 Headings and LabelsDescriptive, hierarchical headings
2.4.7 Focus VisibleVisible focus indicator (2px+ outline)

Best Practices

Semantic HTML First

Use native HTML elements before ARIA. A <button> is better than <div role="button">.

Don't Override Default Behavior

Native elements have built-in accessibility. Don't break it with JavaScript.

Test with Real Users

Automated tools catch ~30% of issues. Manual testing with assistive technology is essential.

Provide Multiple Ways

Offer keyboard, mouse, and touch alternatives for all interactions.

References

For full ARIA widget patterns, keyboard navigation implementations, testing recipes, common fixes, and CSS utilities, see REFERENCE.md.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/laurigates/claude-plugins/accessibility-implementation">View accessibility-implementation on skillZs</a>