astro-a11y

Accessibility patterns for Astro lead generation sites. WCAG 2.1 AA compliance, screen readers, keyboard navigation, focus management, ARIA. Use for all accessibility implementation.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for implementing and verifying WCAG 2.1 AA accessibility standards within Astro-based web projects. It offers specialized patterns for keyboard navigation, screen reader optimization, and ARIA implementation to ensure legal compliance (such as the UK Equality Act 2010) and inclusive user experiences for lead generation sites.

Use Cases

  • Developing keyboard-navigable interfaces with visible focus indicators and logical tab orders to meet accessibility requirements.
  • Ensuring high-conversion lead generation forms are fully accessible with proper semantic labels and ARIA live regions for error announcements.
  • Performing comprehensive accessibility audits using the built-in testing checklist and recommended tools like axe DevTools and WAVE.
  • Implementing 'prefers-reduced-motion' and high-contrast UI components to support users with visual, motor, or vestibular sensitivities.
nameastro-a11y
descriptionAccessibility patterns for Astro lead generation sites. WCAG 2.1 AA compliance, screen readers, keyboard navigation, focus management, ARIA. Use for all accessibility implementation.

Astro Accessibility Skill

Purpose

Ensures WCAG 2.1 AA compliance for lead generation websites. Legal requirement under UK Equality Act 2010. Provides essential patterns for keyboard navigation, screen readers, focus management, and ARIA implementation.

Core Rules

  1. Keyboard navigable — All interactive elements reachable via Tab
  2. Screen reader friendly — Semantic HTML, proper ARIA
  3. Visible focus — Clear focus indicators on all elements
  4. Sufficient contrast — 4.5:1 text, 3:1 UI components
  5. No motion harm — Respect prefers-reduced-motion
  6. Semantic HTML first — Use native elements before ARIA
  7. Labels required — Every form input must have a label
  8. Alternative text — All images need appropriate alt text
Element Use For
<button> Actions (submit, toggle, open modal)
<a href> Navigation (go to page, section)

Color Contrast Requirements

Element Minimum Ratio
Body text 4.5:1
Large text (18px+ or 14px bold) 3:1
UI components 3:1
Disabled elements No requirement

Testing Tools

  • Chrome DevTools → Rendering → Emulate vision deficiencies
  • axe DevTools extension
  • WAVE extension
  • Screen readers: NVDA (Windows), VoiceOver (Mac), JAWS

References

Testing Checklist

Keyboard

  • Tab through entire page — logical order?
  • All interactive elements reachable?
  • Focus visible on every element?
  • Can escape modals with Escape key?
  • Skip link works?

Screen Reader

  • Page title announced?
  • Headings hierarchy correct?
  • Images have alt text?
  • Form labels announced?
  • Errors announced (aria-live)?

Visual

  • Contrast passes (4.5:1)?
  • Text resizes to 200% without breaking?
  • Works without color alone?
  • Reduced motion respected?

Forbidden

  • ❌ <div> or <span> for interactive elements
  • ❌ outline: none without replacement focus style
  • ❌ tabindex greater than 0
  • ❌ Missing form labels
  • ❌ Color as only indicator
  • ❌ Auto-playing video/audio
  • ❌ CAPTCHA without alternative

Definition of Done

  • Skip link present on page
  • All forms have proper labels
  • Contrast ratios pass WCAG AA
  • Keyboard navigation works completely
  • axe DevTools shows 0 errors
  • Screen reader test passed
  • Reduced motion media query implemented
  • All images have appropriate alt text