react-native-accessibility
Skill8 starsChanged 9 months agoMITView on GitHub
Automatically applies accessibility best practices to React Native and Expo projects. Use when working on mobile apps that need VoiceOver (iOS) or TalkBack (Android) support, WCAG compliance, or accessibility audits. Triggers on React Native accessibility tasks, a11y improvements, or when the user mentions accessibility, VoiceOver, TalkBack, or screen reader support.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pchalupa/skillstheir own version, first seen Sep 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pchalupa/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/react-native-accessibility/AGENTS.mdAGENTS.md
- skills/swift-accessibility/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- md-to-pdfSkill
- skill-creatorSkill
- md-to-pdfSkill
- react-native-animationsSkill
- react-native-skia-shadersSkill
- swift-accessibilitySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 82
Check for app.json or app.config.js/app.config.ts to determine if this is an Expo project
- Very specific: line 119
Create accessibility.test.tsx in the project's test directory
- Distinctive: line 120
Add a test case for each screen/component that was modified
- Very specific: line 121
Use @testing-library/react-native with accessibility queries
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
React Native Accessibility
Scan, fix, and audit accessibility in React Native and Expo projects. Detects missing screen reader labels, roles, hints, font scaling issues, WCAG violations, and generates Jest test code. Supports both iOS (VoiceOver) and Android (TalkBack) with platform-specific considerations per rule.
When to Apply
Reference these guidelines when:
- Working on React Native or Expo projects that need accessibility support
- Adding VoiceOver (iOS) or TalkBack (Android) support
- Running an accessibility audit or a11y review
- Fixing font scaling, contrast, or WCAG compliance issues
- Preparing a mobile app for accessibility compliance
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
| 1 | Missing Screen Reader Labels | CRITICAL | p0- |
| 2 | Missing Context and Discoverability | HIGH | p1- |
| 3 | Visual, Interaction, and System Setting Compliance | MEDIUM | p2- |
Quick Reference
1. Missing Screen Reader Labels (CRITICAL)
p0-images-without-labels— Images, ExpoImage, and SVG icons withoutaccessibilityLabelp0-icon-only-pressables— Pressable/TouchableOpacity wrapping only an icon with no label
2. Missing Context and Discoverability (HIGH)
p1-missing-hints— Interactive elements withoutaccessibilityHintp1-missing-roles— Pressable/Touchable withoutaccessibilityRolep1-missing-input-labels—TextInputwithoutaccessibilityLabelp1-small-touch-targets— Interactive elements below 48x48 dp minimump1-color-only-information— Color as the sole means of conveying information
3. Visual, Interaction, and System Setting Compliance (MEDIUM)
p2-font-scaling-disabled—allowFontScaling={false}or lowmaxFontSizeMultiplierp2-ungrouped-elements— Related elements (icon + text) not grouped for screen readersp2-missing-header-roles— Section titles withoutaccessibilityRole="header"p2-decorative-elements-exposed— Decorative images/separators in the accessibility treep2-contrast-insufficient— Colors that fail WCAG AA contrast ratiosp2-reduce-motion-ignored— Animations without reduce-motion checkp2-custom-actions-missing— Swipe/long-press gestures withoutaccessibilityActionsp2-live-region-missing— Dynamic content updates not announced to screen readersp2-modal-focus-management— Custom modals without focus trapping or background hiding
WCAG AA Coverage
| WCAG Criterion | Rules Covering It |
| 1.1.1 Non-text Content | p0-images-without-labels, p0-icon-only-pressables, p2-decorative-elements-exposed |
| 1.3.1 Info and Relationships | p2-ungrouped-elements, p2-missing-header-roles |
| 1.4.1 Use of Color | p1-color-only-information |
| 1.4.3 Contrast (Minimum) | p2-contrast-insufficient |
| 1.4.4 Resize Text | p2-font-scaling-disabled |
| 2.5.5 Target Size | p1-small-touch-targets |
| 4.1.2 Name, Role, Value | p1-missing-roles, p1-missing-hints, p1-missing-input-labels |
| 4.1.3 Status Messages | p2-live-region-missing |
Workflow
Execute these 5 phases in order. Load rule files on-demand — only read a rule when its content is needed for the current phase.
Phase 1: Project Discovery
- Check for
app.jsonorapp.config.js/app.config.tsto determine if this is an Expo project - Glob for
**/*.{tsx,jsx,ts,js}to find all React Native source files - Identify navigation library:
@react-navigation/*,expo-router, etc. - Grep for existing accessibility usage to understand current coverage:
accessibilityLabel,accessibilityHint,accessibilityRoleaccessibilityState,accessibilityValue,accessibilityActionsaccessibilityLiveRegion,accessibilityViewIsModalaccessible={false},importantForAccessibility
- Report: total files, Expo vs bare RN, navigation library, current accessibility coverage percentage
Phase 2: Issue Detection
Scan files for anti-patterns. Read rules from rules/ directory for detection patterns.
For each issue found, record: file path, line number, priority, description, and suggested fix.
Phase 3: Automated Fixes
Apply fixes using Edit tool, following these rules:
- Never overwrite existing accessibility code — only add missing properties
- Add
[VERIFY]comment markers on generated labels where semantic accuracy needs human review:accessibilityLabel="Settings icon" // [VERIFY] confirm label matches intent - Preserve formatting — match the indentation and style of surrounding code
- Group related fixes — apply all fixes to a single element together
Fix application order:
- P0 Critical fixes first
- P1 High fixes
- P2 Medium fixes (comprehensive mode only)
Phase 4: Test Generation
Load assets/jest-a11y-test-template.tsx and generate a Jest test file for the project.
- Create
accessibility.test.tsxin the project's test directory - Add a test case for each screen/component that was modified
- Use
@testing-library/react-nativewith accessibility queries - Include setup for navigation context if needed
Match the project's existing test framework and patterns.
Phase 5: Report
Output a structured summary:
## Accessibility Audit Report
### Issues Found
| Priority | Category | Count |
|----------|----------|-------|
| P0 Critical | ... | ... |
| P1 High | ... | ... |
| P2 Medium | ... | ... |
### Changes Applied
- **Files modified**: [list]
- **Issues fixed**: [count] of [total]
- **Test file generated**: [path]
### Platform Coverage
| Feature | iOS (VoiceOver) | Android (TalkBack) |
|---------|-----------------|-------------------|
| Screen reader labels | Ready / Needs Work | Ready / Needs Work |
| Roles and hints | Ready / Needs Work | Ready / Needs Work |
| Touch targets | Ready / Needs Work | Ready / Needs Work |
| Font scaling | Ready / Needs Work | Ready / Needs Work |
| Reduce motion | Ready / Needs Work | Ready / Needs Work |
### Manual Review Required
Items marked with [VERIFY] that need human confirmation:
- [list of VERIFY items with file:line references]
### Next Steps
- [ ] Run VoiceOver testing on iOS (see assets/checklist.md)
- [ ] Run TalkBack testing on Android (see assets/checklist.md)
- [ ] Review [VERIFY] markers and update labels
- [ ] Run generated accessibility tests
- [ ] Test with maximum system font size on both platforms
- [ ] Test with Reduce Motion enabled on both platforms
- [ ] Verify color contrast with a contrast checker toolConfiguration
- Standard mode (default): Fixes P0 and P1 issues, reports P2
- Comprehensive mode: Fixes all priority levels — invoke with "comprehensive" or "full audit"
Supporting Files
Loaded on-demand during execution:
rules/— Individual detection and fix rules per issue category (16 rules)references/react-native-a11y-api.md— Full React Native accessibility API catalogreferences/platform-differences.md— iOS vs Android accessibility behavior differencesreferences/wcag-guidelines.md— WCAG AA and platform guideline referenceassets/jest-a11y-test-template.tsx— Jest accessibility test templateassets/checklist.md— Manual verification checklist for both platforms
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

