Index of every page on this site: llms.txt
All skills
neha avatar

/accessibility

@eb9f097
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/neha/rn-developer-skills/accessibility

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈615 when used: this file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈232 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

<TouchableOpacity onPress={onDelete}>
  <Icon name="trash" />
</TouchableOpacity>

Correct:

<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)

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: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    This skill provides a documentation-based checklist for auditing React Native accessibility. No security issues or malicious patterns were detected.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at eb9f097. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
version
1.1.0
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "accessibility",
  "a11y",
  "screen-reader"
]

README badge

README badge for neha/rn-developer-skills/accessibility