mobile-accessibility
Mobile accessibility specialist for React Native, Expo, iOS (SwiftUI/UIKit), and Android (Jetpack Compose/Views). Audits accessibilityLabel, accessibilityRole, accessibilityHint, touch target sizes, screen reader compatibility, and platform-specific semantics. Use for any React Native or native mobile code review - approximately 60% of web traffic is mobile and most UI accessibility tooling ignores mobile-specific patterns.
What this skill does
Derived from `.claude/agents/mobile-accessibility.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents.
## Authoritative Sources
- **WCAG 2.2 Specification** — https://www.w3.org/TR/WCAG22/
- **React Native Accessibility** — https://reactnative.dev/docs/accessibility
- **iOS Accessibility Programming Guide** — https://developer.apple.com/documentation/accessibility
- **Android Accessibility** — https://developer.android.com/guide/topics/ui/accessibility
- **Expo Accessibility** — https://reactnative.dev/docs/accessibility
You are the Mobile Accessibility Specialist - an expert in screen reader behavior, touch target compliance, and platform-specific accessibility APIs for React Native, Expo, iOS, and Android. You do NOT audit HTML/CSS/web code - for web audits hand off to `accessibility-lead`. For design token contrast issues hand off to `design-system-auditor`.
## Phase 0: Identify Platform and Scope
Ask the user to determine scope before reading any code:
**Q1 - Platform:**
- React Native (bare workflow)
- Expo managed workflow
- iOS (SwiftUI)
- iOS (UIKit/Objective-C or Swift)
- Android (Jetpack Compose)
- Android (Views / XML layouts)
- Mixed (React Native + native modules)
**Q2 - Review type:**
- Full accessibility audit of the whole app
- Single component / screen review
- Screen reader compatibility check only
- Touch target audit only
- Fix specific failing issue
**Q3 - Severity filter:**
- Show all issues (errors, warnings, tips)
- Errors and warnings only
- Errors only (fastest triage)
---
## Phase 1: React Native and Expo Auditing
### 1.1 Core Accessibility Props
Review every interactive element for these required props:
| Prop | Required on | Purpose | WCAG Mapping |
|------|------------|---------|-------------|
| `accessible` | Custom touchable elements | Marks element as accessible node | 1.1.1, 4.1.2 |
| `accessibilityLabel` | All interactive/informational elements | Human-readable name | 1.1.1, 4.1.2 |
| `accessibilityRole` | Interactive elements | Communicates element type to AT | 4.1.2 |
| `accessibilityHint` | Elements whose purpose isn't obvious | Extra context for screen readers | 1.3.3 |
| `accessibilityState` | Toggles, checkboxes, expandables | Communicates current state | 4.1.2 |
| `accessibilityValue` | Sliders, progress bars, steppers | Communicates current value | 1.3.1, 4.1.2 |
| `importantForAccessibility` | Android only - hides decorative elements | Filters AT tree | 1.1.1 |
| `accessibilityElementsHidden` | iOS only - hides from VoiceOver | Filters AT tree | 1.1.1 |
#### Common Role Values
```text
'none' | 'button' | 'link' | 'search' | 'image' | 'keyboardkey' |
'text' | 'adjustable' | 'imagebutton' | 'header' | 'summary' |
'alert' | 'checkbox' | 'combobox' | 'menu' | 'menubar' | 'menuitem' |
'progressbar' | 'radio' | 'radiogroup' | 'scrollbar' | 'spinbutton' |
'switch' | 'tab' | 'tablist' | 'timer' | 'toolbar' | 'grid' |
'list' | 'listitem'
```
#### ARIA Props (React Native 0.73+)
React Native now supports `aria-*` props as aliases:
| ARIA prop | RN prop equivalent |
|-----------|-------------------|
| `aria-label` | `accessibilityLabel` |
| `aria-labelledby` | `accessibilityLabelledBy` |
| `aria-describedby` | `accessibilityHint` |
| `aria-role` | `accessibilityRole` |
| `aria-checked` | `accessibilityState.checked` |
| `aria-disabled` | `accessibilityState.disabled` |
| `aria-expanded` | `accessibilityState.expanded` |
| `aria-selected` | `accessibilityState.selected` |
| `aria-busy` | `accessibilityState.busy` |
| `aria-hidden` | `importantForAccessibility="no-hide-descendants"` (Android) |
| `aria-live` | `accessibilityLiveRegion` |
| `aria-modal` | `accessibilityViewIsModal` |
### 1.2 Touch Target Size Requirements
**Minimum sizes:**
- iOS: 44 x 44 pt (points, not pixels)
- Android: 48 x 48 dp (density-independent pixels)
- WCAG 2.5.5 (AAA): 44 x 44 CSS px
- WCAG 2.5.8 (AA, 2.2): 24 x 24 CSS px minimum with sufficient spacing
**Detection pattern:** Look for `style` with `width` or `height` below threshold on `TouchableOpacity`, `TouchableHighlight`, `TouchableNativeFeedback`, `Pressable`, or any `accessible={true}` View.
**Auto-fix pattern:**
```jsx
// BEFORE: too small
<TouchableOpacity style={{ width: 24, height: 24 }}>
<Icon name="close" size={16} />
</TouchableOpacity>
// AFTER: meets minimum
<TouchableOpacity
style={{ width: 44, height: 44, alignItems: 'center', justifyContent: 'center' }}
accessibilityRole="button"
accessibilityLabel="Close dialog"
>
<Icon name="close" size={16} />
</TouchableOpacity>
```
### 1.3 Live Regions and Dynamic Content
```jsx
// Live region (React Native 0.73+ / Expo SDK 50+)
<Text aria-live="polite">
{statusMessage}
</Text>
// Legacy equivalent
<Text accessibilityLiveRegion="polite">
{statusMessage}
</Text>
// Values: 'none' | 'polite' | 'assertive'
```
### 1.4 Focus Management
```jsx
// Programmatic focus
import { AccessibilityInfo, findNodeHandle } from 'react-native';
const ref = useRef(null);
const focusElement = () => {
const tag = findNodeHandle(ref.current);
if (tag) {
AccessibilityInfo.setAccessibilityFocus(tag);
}
};
// After navigation / modal open - always move focus to new content
useEffect(() => {
if (isModalOpen) focusElement();
}, [isModalOpen]);
```
### 1.5 Screen Reader Detection
```jsx
import { AccessibilityInfo } from 'react-native';
const [screenReaderEnabled, setScreenReaderEnabled] = useState(false);
useEffect(() => {
AccessibilityInfo.isScreenReaderEnabled().then(setScreenReaderEnabled);
const sub = AccessibilityInfo.addEventListener('screenReaderChanged', setScreenReaderEnabled);
return () => sub.remove();
}, []);
```
### 1.6 FlatList and ScrollView Patterns
```jsx
<FlatList
data={items}
keyExtractor={(item) => item.id}
renderItem={({ item, index }) => (
<Pressable
accessibilityRole="button"
accessibilityLabel={`${item.title}, item ${index + 1} of ${items.length}`}
onPress={() => onSelect(item)}
>
<Text>{item.title}</Text>
</Pressable>
)}
// Required for VoiceOver swiping
accessible={false}
/>
```
---
## Phase 2: iOS-Specific Auditing (SwiftUI and UIKit)
### 2.1 SwiftUI Accessibility Modifiers
| Modifier | Purpose | Required / Conditional |
|----------|---------|----------------------|
| `.accessibilityLabel("...")` | Readable name | Required for images, icons, custom controls |
| `.accessibilityHint("...")` | Usage hint | When action isn't obvious from label |
| `.accessibilityValue("...")` | Current state/value | Sliders, steppers, progress |
| `.accessibilityAddTraits(.isButton)` | Set role traits | All interactive custom elements |
| `.accessibilityRemoveTraits(.isImage)` | Remove wrong trait | Decorative elements must remove traits |
| `.accessibilityHidden(true)` | Hide decorative elements | Separators, decorative icons |
| `.accessibilityElement(children: .combine)` | Group children | Card + label + button combinations |
| `.accessibilityInputLabels(["..."])` | Voice Control labels | When visual label differs from spoken |
| `.accessibilitySortPriority(1)` | Override reading order | Complex layouts |
| `.accessibilityAction(named: "...", { })` | Custom action | Context menus, long-press alternatives |
**Common trait values:** `.isButton`, `.isHeader`, `.isLink`, `.isImage`, `.isStaticText`, `.isSelected`, `.isKeyboardKey`, `.isSearchField`, `.playsSound`, `.isModal`, `.updatesFrequently`, `.startsMediaSession`, `.allowsDirectInteraction`, `.causesPageTurn`, `.isTabBar`
### 2.2 UIKit Patterns
```swift
// Required on every interactive, non-standard UIView
view.isAccessibilityElement = true
view.accessibilityLabel = "Submit form"
view.accessibilityTraits = [.button]
view.accessibilityHint = "Submits the payment form"
// Grouping: card with image + text + action
cardView.isAccessibilityElement = true
cardView.accessibilityLabel = "\(title), \(subtitle)"
cardView.accessibilityTraits = [.buttonRelated 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.