framework-accessibility

Provide framework-specific accessibility patterns and code fixes for React, Next.js, Vue, Angular, Svelte, and Tailwind CSS.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill framework-accessibility-community-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: framework-accessibility
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/framework-accessibility
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill framework-accessibility-community-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common accessibility pitfalls and anti-patterns specific to popular web development frameworks, helping developers create more inclusive user interfaces.

Core Features & Use Cases

  • Framework-Specific Guidance: Provides detailed common pitfalls and fix templates for React/Next.js, Vue, Angular, Svelte, and Tailwind CSS.
  • Code Snippet Examples: Offers clear "bad" vs. "good" code examples for quick understanding and implementation.
  • Contrast-Safe Utility: Includes a table of Tailwind CSS class pairs that meet WCAG contrast requirements.
  • Use Case: When building a new component in React, consult this Skill to avoid common mistakes like using div for clickable elements or neglecting focus management on route changes.

Quick Start

Use the framework-accessibility skill to identify and fix a common accessibility pitfall in a React component.

Frequently Asked Questions about framework-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix common React accessibility pitfalls like using div for clickable elements?

Fix React accessibility pitfalls by replacing div elements with semantic buttons or links and implementing proper focus management. This Skill provides specific bad vs. good code fix templates for React and Next.js components to ensure correct keyboard navigation.

Does Tailwind CSS meet WCAG AA color contrast requirements out of the box?

Tailwind CSS does not automatically guarantee WCAG AA color contrast compliance. This Skill provides a contrast-safe utility table mapping specific Tailwind CSS class pairs that meet the required contrast ratios for accessible web development.

What is the best way to handle focus management on route changes in Vue or Svelte?

Handle focus management on route changes by programmatically moving focus to the new page content or skip links. This Skill offers framework-specific accessibility patterns and code fix templates for Vue and Svelte to maintain keyboard navigation during route transitions.

How do I implement ARIA attributes correctly in Angular components?

Implement ARIA attributes in Angular by applying framework-specific accessibility patterns that avoid common anti-patterns. This Skill details common ARIA implementation pitfalls and provides code snippet examples to ensure proper screen reader support.

Can I use this to check keyboard navigation across different web frameworks?

Yes, you can check keyboard navigation patterns across React, Vue, Angular, and Svelte. This Skill addresses framework-specific keyboard navigation issues and provides code examples to fix inaccessible component interactions.

Why does my accessible web component still fail WCAG AA compliance checks?

Accessible web components fail WCAG AA checks due to common framework-specific pitfalls like neglected focus management or incorrect ARIA implementation. This Skill identifies these anti-patterns and provides utility tables to fix contrast and navigation issues.