Skip to content
Skills Library
Programming · Review & audit

accessibility

/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.

Author
neha ↗
Licence
MIT
Last repository change
29.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Applicability
  2. When to Use
  3. Severity
  4. Guidance
  5. Pitfalls
Original SKILL.md headings · 70 lines, 356 words
SKILL.md preview
---
name: accessibility
description: 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.
version: 1.1.0
platforms: [ios, android]
react-native-version: 0.76+
tags: [react-native, accessibility, a11y, screen-reader]
---

# 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

## Severity

- **Merge-blocking:** an interactive control this diff adds has no accessible name.
- **Should-fix:** target size, contrast, dynamic type, and focus order.

## Guidance

### Labels & Roles

- [ ] An interactive control has an accessible name: its visible text, or an `accessibilityLabel` when the visible content is only an icon
- [ ] Do not repeat the visible text in `accessibilityLabel`
- [ ] Every interactive element has an `accessibilityRole` (button, link, header, etc.)
- [ ] State changes use `accessibilityState` (disabled, selected, expanded)
- [ ] Images have an `accessibilityLabel`, or are marked `accessibilityElementsHidden` if decorative
- [ ] Dynamic content changes are announced (`AccessibilityInfo.announceForAccessibility`)

**Incorrect:**
```tsx
<TouchableOpacity onPress={onDelete}>
  <Icon name="trash" />
</TouchableOpacity>
```

**Correct:**
```tsx
<TouchableOpacity
  onPress={onDelete}
  accessibilityLabel="Delete item"
  accessibilityRole="button"
  hitSlop={{ top: 10, bottom: 10, left: 10, right: 10 }}
>
  <Icon name="trash" />
</TouchableOpacity>
```

### Touch & Focus

- [ ] Touch targets are at least 44×44pt on iOS and 48×48dp on Android
- [ ] Focus order follows reading order. In an RTL layout that order starts at the trailing edge (see [i18n-and-localization](../i18n-and-localization/SKILL.md))

### 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.

Versions

RepositoryScoreLicence
This page · neha/rn-developer-skills100MIT
ericrisco/rsc-harness100MIT
Sanit-mann/The-Insectoids100MIT
evanca/flutter-ai-rules100MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
xobotyi/cc-foundry100MIT
krzysztofsurdy/code-virtuoso100MIT
andreibesleaga/gabbe100CC-BY-4.0

Database snapshot: 13.11.2026 · package version 828ecc6a015e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100wp-accessibility-review
    WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility…
  • 90mobile-accessibility
    Audits and fixes mobile accessibility across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including shared Compose UI and native hosts. Covers TalkBack/VoiceOver labels, roles, state, reading order, touch targets, text scaling, contrast and focus.…
  • 100accessibility-a11y
    Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
  • 100flutter-accessibility
    Use when implementing or auditing accessibility on a Flutter screen — the Semantics widget, screen-reader labels (TalkBack/VoiceOver), colour contrast, minimum tap-target size, system font scaling, or semantics in a web build. Also triggers on "make this accessible", "a11y", or…
  • 100game-ui-accessibility-qa
    Use to audit game UI contrast, touch targets, safe areas, overflow, text clipping and focus; not to implement menus.
  • 100accessible-tables
    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.