tailwindcss-accessibility
Tailwind CSS accessibility patterns including WCAG 2.2 compliance, touch targets, focus management, and ARIA. PROACTIVELY activate for: (1) building accessible UI with Tailwind, (2) WCAG 2.2 compliance (Level A, AA, AAA), (3) focus rings and focus-visible styling, (4) minimum touch-target sizes (24x24/44x44), (5) color contrast and text legibility, (6) screen-reader-only utilities (sr-only, not-sr-only), (7) prefers-reduced-motion handling, (8) ARIA attribute styling (data-state, aria-* selectors), (9) keyboard navigation patterns, (10) accessible forms (label association, error announcements). Provides: WCAG 2.2 checklist, focus-management utilities, touch-target sizing recipes, sr-only patterns, and accessible component templates.
What this skill does
# Tailwind CSS Accessibility Patterns (WCAG 2.2 - 2025/2026)
## WCAG 2.2 Overview (Current Standard)
WCAG 2.2 is the current W3C standard. Key Tailwind-relevant additions:
- **2.5.8 Target Size (Level AA)**: 24x24 CSS pixels minimum, 44x44 recommended
- **2.4.11 Focus Not Obscured**: Focus indicators must be visible
- **2.4.13 Focus Appearance**: Enhanced focus indicator requirements
- **3.3.7 Redundant Entry**: Don't require re-entering information
- **3.2.6 Consistent Help**: Help mechanisms in consistent locations
## Focus Management
### Focus Ring Utilities
```html
<!-- Default focus ring -->
<button class="focus:outline-none focus:ring-2 focus:ring-brand-500 focus:ring-offset-2">
Button
</button>
<!-- Focus-visible for keyboard users only -->
<button class="focus:outline-none focus-visible:ring-2 focus-visible:ring-brand-500">
Only shows ring for keyboard focus
</button>
<!-- Focus-within for parent containers -->
<div class="focus-within:ring-2 focus-within:ring-brand-500 rounded-lg p-1">
<input type="text" class="border-none focus:outline-none" />
</div>
<!-- Custom focus ring component -->
```
```css
@layer components {
.focus-ring {
@apply focus:outline-none focus-visible:ring-2 focus-visible:ring-brand-500 focus-visible:ring-offset-2;
}
.focus-ring-inset {
@apply focus:outline-none focus-visible:ring-2 focus-visible:ring-brand-500 focus-visible:ring-inset;
}
}
```
### Skip Links
```html
<!-- Skip to main content -->
<a
href="#main-content"
class="
sr-only focus:not-sr-only
focus:absolute focus:top-4 focus:left-4 focus:z-50
focus:bg-white focus:px-4 focus:py-2 focus:rounded-md focus:shadow-lg
focus:ring-2 focus:ring-brand-500
"
>
Skip to main content
</a>
<header>Navigation...</header>
<main id="main-content" tabindex="-1">
Main content
</main>
```
### Focus Trap Pattern
```html
<!-- Modal with focus management -->
<div
role="dialog"
aria-modal="true"
aria-labelledby="modal-title"
class="fixed inset-0 z-50 flex items-center justify-center"
>
<div class="fixed inset-0 bg-black/50" aria-hidden="true"></div>
<div
class="relative bg-white rounded-xl p-6 max-w-md w-full"
role="document"
>
<h2 id="modal-title" class="text-lg font-semibold">Modal Title</h2>
<p>Modal content</p>
<button class="focus-ring">Close</button>
</div>
</div>
```
## Screen Reader Utilities
### Visually Hidden Content
```html
<!-- Hidden visually but available to screen readers -->
<span class="sr-only">Additional context for screen readers</span>
<!-- Show on focus (skip links) -->
<a href="#main" class="sr-only focus:not-sr-only">Skip to main</a>
<!-- Icon with accessible label -->
<button>
<svg aria-hidden="true">...</svg>
<span class="sr-only">Close menu</span>
</button>
<!-- Form labels -->
<label>
<span class="sr-only">Search</span>
<input type="search" placeholder="Search..." />
</label>
```
### Announcing Dynamic Content
```html
<!-- Live region for announcements -->
<div
role="status"
aria-live="polite"
aria-atomic="true"
class="sr-only"
>
<!-- Dynamic content announced to screen readers -->
3 items added to cart
</div>
<!-- Alert for important messages -->
<div
role="alert"
aria-live="assertive"
class="bg-red-100 text-red-800 p-4 rounded-lg"
>
Error: Please correct the form
</div>
```
## Color Contrast
### High Contrast Patterns
```html
<!-- Ensure sufficient contrast -->
<p class="text-gray-700 bg-white">4.5:1 contrast ratio</p>
<p class="text-gray-500 bg-white">May not meet WCAG AA (3:1 min for large text)</p>
<!-- Large text (18pt+) needs 3:1 -->
<h1 class="text-4xl text-gray-600 bg-white">Large text - 3:1 ratio OK</h1>
<!-- Interactive elements need 3:1 against adjacent colors -->
<button class="
bg-brand-500 text-white
border-2 border-brand-500
focus:ring-2 focus:ring-brand-500 focus:ring-offset-2
">
Accessible Button
</button>
```
### Dark Mode Contrast
```html
<!-- Maintain contrast in both modes -->
<p class="text-gray-900 dark:text-gray-100">
High contrast text
</p>
<p class="text-gray-600 dark:text-gray-400">
Secondary text with adequate contrast
</p>
<!-- Avoid low contrast combinations -->
<p class="text-gray-400 dark:text-gray-600">
⚠️ May have contrast issues in dark mode
</p>
```
### Focus Indicator Contrast
```css
@theme {
/* High contrast focus ring */
--color-focus: oklch(0.55 0.25 250);
--color-focus-offset: oklch(1 0 0);
}
```
```html
<button class="
focus:outline-none
focus-visible:ring-2
focus-visible:ring-[var(--color-focus)]
focus-visible:ring-offset-2
focus-visible:ring-offset-[var(--color-focus-offset)]
">
High contrast focus
</button>
```
## Motion and Animation
### Reduced Motion
```html
<!-- Respect user's motion preferences -->
<div class="
animate-bounce
motion-reduce:animate-none
">
Bouncing element (static for motion-sensitive users)
</div>
<!-- Safer alternative animations -->
<div class="
transition-opacity duration-300
motion-reduce:transition-none
">
Fades in (instant for motion-sensitive)
</div>
<!-- Use opacity instead of movement -->
<div class="
transition-all
hover:scale-105 hover:shadow-lg
motion-reduce:hover:scale-100 motion-reduce:hover:shadow-md
">
Scales on hover (shadow only for motion-sensitive)
</div>
```
### Safe Animation Patterns
```css
@layer components {
/* Animations that respect reduced motion */
.animate-fade-in {
@apply animate-in fade-in duration-300;
@apply motion-reduce:animate-none motion-reduce:opacity-100;
}
.animate-slide-up {
@apply animate-in slide-in-from-bottom-4 duration-300;
@apply motion-reduce:animate-none motion-reduce:translate-y-0;
}
}
```
### Pause Animation on Hover
```html
<!-- Allow users to pause animations -->
<div class="
animate-spin
hover:animate-pause
motion-reduce:animate-none
">
Loading spinner
</div>
```
## Form Accessibility
### Accessible Form Fields
```html
<div class="space-y-4">
<!-- Text input with label -->
<div>
<label for="email" class="block text-sm font-medium text-gray-700">
Email address
<span class="text-red-500" aria-hidden="true">*</span>
</label>
<input
type="email"
id="email"
name="email"
required
aria-required="true"
aria-describedby="email-hint email-error"
class="
mt-1 block w-full rounded-md border-gray-300
focus:border-brand-500 focus:ring-brand-500
aria-invalid:border-red-500 aria-invalid:ring-red-500
"
/>
<p id="email-hint" class="mt-1 text-sm text-gray-500">
We'll never share your email
</p>
<p id="email-error" class="mt-1 text-sm text-red-600 hidden" role="alert">
Please enter a valid email
</p>
</div>
<!-- Checkbox with accessible label -->
<div class="flex items-start gap-3">
<input
type="checkbox"
id="terms"
name="terms"
class="
h-4 w-4 rounded border-gray-300 text-brand-500
focus:ring-brand-500
"
/>
<label for="terms" class="text-sm text-gray-700">
I agree to the
<a href="/terms" class="text-brand-500 underline">terms and conditions</a>
</label>
</div>
<!-- Radio group -->
<fieldset>
<legend class="text-sm font-medium text-gray-700">Notification preference</legend>
<div class="mt-2 space-y-2">
<div class="flex items-center gap-3">
<input type="radio" id="email-pref" name="notification" value="email" class="h-4 w-4" />
<label for="email-pref">Email</label>
</div>
<div class="flex items-center gap-3">
<input type="radio" id="sms-pref" name="notification" value="sms" class="h-4 w-4" />
<label for="sms-pref">SMS</label>
</div>
</div>
</fieldset>
</div>
```
### Error States
```html
<!-- Input with error -->
<div>
<label for="password" class="block text-sm font-medium text-gray-700">
Password
</label>
<input
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.