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.
Best use case
astro-a11y is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Accessibility patterns for Astro lead generation sites. WCAG 2.1 AA compliance, screen readers, keyboard navigation, focus management, ARIA. Use for all accessibility implementation.
Teams using astro-a11y should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/astro-a11y/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How astro-a11y Compares
| Feature / Agent | astro-a11y | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Accessibility patterns for Astro lead generation sites. WCAG 2.1 AA compliance, screen readers, keyboard navigation, focus management, ARIA. Use for all accessibility implementation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ## Buttons vs Links | 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 - [Semantic HTML Patterns](references/semantic-html.md) - [Focus Management](references/focus-management.md) — Skip links, focus traps, focus visible styles - [ARIA Patterns](references/aria-patterns.md) — Live regions, mobile menus - [Form Accessibility](references/forms.md) — Labels, error messages, required fields - [Image Accessibility](references/images.md) — Alt text patterns - [Motion & Animation](references/motion-animation.md) — Reduced motion support - [Screen Reader Only Utility](references/screen-reader-only.md) — SR-only CSS class ## 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
Related Skills
astrologue-ia
Expert astrologique brutal et transparent. Analyse thème natal (stelliums, aspects, maisons), synastrie/compatibilité (scores, red flags, comparaison multiple), transits et prévisions (dates clés, timing optimal), astrocartographie (meilleurs lieux de vie). Style direct, zéro bullshit, full transparence. Fetch automatique des données astro depuis astro-seek.com. Use when analyzing birth charts, compatibility, astrological timing, or best places to live based on astrology.
astro-animations
Animation patterns for Astro sites. Scroll animations, micro-interactions, transitions, loading states. Performance-focused, accessibility-aware.
astro-cta-injector
Inject Call-to-Action blocks into Astro site content with intelligent placement strategies. Use when the user wants to add CTAs, newsletter signups, product promotions, or any content blocks to blog posts. Supports multiple placement strategies (end, after 50%, after 60%), content scoring for relevance, and dry-run preview.
astro-content
Create Astro/Starlight MDX content pages. Use when the user says "write a new article", "add a blog post", "create content in Tech/Life category", or "add an MDX page".
astro-blog-write
Phase 3 - Writing blog content with human voice and SEO optimization
astro-i18n
Internationalization patterns for Astro sites. Multi-language routing, content translation, locale switching, RTL support. Use for multi-market lead generation.
managing-astro-local-env
Manage local Airflow environment with Astro CLI. Use when the user wants to start, stop, or restart Airflow, view logs, troubleshoot containers, or fix environment issues. For project setup, see setting-up-astro-project.
astro-seo
SEO markup patterns for Astro lead generation sites. Meta tags, Open Graph, Schema.org, sitemap, robots. Use for all SEO implementation.
astro-performance
Core Web Vitals and performance optimization for Astro sites. LCP, CLS, INP optimization, bundle size, fonts, third-party scripts. Use for performance tuning.
astro-forms
Form infrastructure for Astro. Zod validation, email, rate limiting, Turnstile, GDPR, Sheets. FAIL = no conversion.
astro-aso
Query local Astro Mac app database for ASO insights. Use when the user asks about keyword rankings, historical ranking data, trend analysis, competitor keywords, app ratings, keyword opportunities, or ASO health metrics.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.