Accessibility
Review React Native code for screen-reader support, labels and roles, touch targets, focus order, colour contrast, and dynamic type. Use when building UI, reviewing components, or auditing a screen for accessibility.
Install
$ agentstack add skill-neha-rn-developer-skills-accessibility ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-neha-rn-developer-skills-accessibility) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Accessibility Skill
Applicability
- Platforms: iOS and Android
- React Native: 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)
When to Use
- Building or reviewing any interactive UI
- Auditing a screen for screen-reader and assistive-technology support
- Verifying an app meets accessibility expectations before release
Guidance
Labels & Roles
- [ ] Every interactive element has an
accessibilityLabelthat describes its purpose, not its type - [ ] Every interactive element has an
accessibilityRole(button, link, header, etc.) - [ ] State changes use
accessibilityState(disabled, selected, expanded) - [ ] Images have an
accessibilityLabel, or are markedaccessibilityElementsHiddenif decorative - [ ] Dynamic content changes are announced (
AccessibilityInfo.announceForAccessibility)
Incorrect:
Correct:
Touch & Focus
- [ ] Touch targets are at least 44x44pt
- [ ] Focus order is logical (top to bottom, left to right)
Visual
- [ ] Colour is not the only indicator of state (add icon, text, or pattern)
- [ ] Text scales with the system font-size preference
Verification
- [ ] Tested with VoiceOver (iOS) and TalkBack (Android)
Pitfalls
- Labels that describe the element type ("button") instead of its purpose ("Delete item") give screen-reader users no useful information.
- Forgetting
accessibilityState={{ disabled: true }}on a disabled control means the screen reader still announces it as an active button. - Relying on colour alone (e.g. red for error) excludes colour-blind users; pair it with an icon or text.
- Fixed font sizes break layouts when users increase system text size — test at large dynamic type settings.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Neha
- Source: Neha/rn-developer-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.