Agent skill

Mobile Accessibility

by Community-Access in Community-Access/accessibility-agents

React Native, Expo, iOS and Android: labels, roles and touch targets.

MITAuto-check passedMobile

Install Mobile Accessibility

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill mobile-accessibility -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Community-Access/accessibility-agents mobile-accessibility --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mobile-accessibility .claude/skills/mobile-accessibility && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-accessibility
GitHub stars
422
Token cost
~1.1k tokens
SKILL.md length
273 words
Files
3 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

React Native, Expo, iOS and Android: labels, roles and touch targets.

  • Works in 3 steps: Identify Platform and Scope → Testing Guidance → Report Format
  • Tasks that involve Accessibility
  • SKILL.md covers Phase 0: Identify Platform and…, Phase 4: Testing Guidance, Phase 5: Report Format and Handoffs, plus 2 more sections
  • Calls adb

What it does

Mobile Accessibility is an agent skill from Community-Access/accessibility-agents. React Native, Expo, iOS and Android: labels, roles and touch targets.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/phase-1-react-native-and-expo-auditing.md`).

It sits in Mobile, covering Accessibility, Cross-platform mobile apps and Mobile UI design. It works with React Native, iOS, Expo and Android. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility
  • Tasks that involve Cross-platform mobile apps
  • Tasks that involve Mobile UI design

Example prompts

  • “/mobile-accessibility”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Identify Platform and Scope
  2. Testing Guidance
  3. Report Format

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • adb

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile Accessibility loads about 1.1k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 23 tokens; SKILL.md has 273 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 273 words, ~1,100 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-accessibility/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
mobile-accessibility
description
React Native, Expo, iOS and Android: labels, roles and touch targets.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
web
metadata.output
findings
metadata.effort
medium
metadata.title
Mobile 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 4: Testing Guidance

4.1 Manual Testing with Platform Tools

iOS - Xcode Accessibility Inspector:

text
Xcode -> Xcode menu -> Open Developer Tool -> Accessibility Inspector
- Run audit: Audit tab -> Run Audit
- Inspect elements: Inspection tab -> hover element
- Simulate VoiceOver: +F7 in Simulator

Android - Accessibility Scanner:

text
Install: Play Store -> "Accessibility Scanner" (Google)
Use: Overlay -> tap blue checkmark -> scan screen
Output: Issues list with severity and suggested fixes

React Native - Debugging:

bash
# Android TalkBack via ADB
adb shell settings put secure enabled_accessibility_services \
  com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService

# Check accessibility tree (RN)
# In Metro: press 'a' for Android accessibility report
4.2 Automated Testing

React Native Testing Library:

jsx
import { render, screen } from '@testing-library/react-native';

test('close button is accessible', () => {
  render(<CloseButton onPress={jest.fn()} />);

  const button = screen.getByRole('button', { name: /close/i });
  expect(button).toBeTruthy();
  expect(button).toHaveAccessibilityState({ disabled: false });
});

Detox (E2E + accessibility):

js
// Check accessibility label
await expect(element(by.label('Submit form'))).toBeVisible();

// Verify role
await expect(element(by.id('submit-btn'))).toHaveRole('button');

Maestro:

yaml
- assertVisible:
    label: "Close dialog"
- tapOn:
    label: "Submit form"

Phase 5: Report Format

Structure the accessibility report as follows:

markdown
## Mobile Accessibility Audit - [Component/Screen Name]
**Platform:** React Native / iOS / Android
**Date:** YYYY-MM-DD
**Severity Filter:** All Issues / Errors + Warnings / Errors Only

### Summary
| Severity | Count |
|----------|-------|
| Error | N |
| Warning | N |
| Tip | N |

### Issues

#### [RN-001 / iOS-001 / AND-001] [Short Description]
- **Severity:** Error | Warning | Tip
- **File:** path/to/Component.tsx (line N)
- **WCAG:** [SC number] - [Name]
- **Impact:** [Who is affected and how]
- **Current code:** `<code snippet>`
- **Fix:** `<corrected code snippet>`

Handoffs

  • Web audit needed? -> hand off to accessibility-lead
  • Design token contrast failures? -> hand off to design-system-auditor
  • WCAG success criteria questions? -> hand off to wcag-guide
  • Screen reader testing guidance? -> hand off to testing-coach

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/phase-1-react-native-and-expo-auditing.md - Phase 1: React Native and Expo Auditing, Phase 2: iOS-Specific Auditing (SwiftUI and UIKit)...

Output contract

Return only JSON matching skills/a11y-core/schemas/findings.schema.json. No prose, no summary, no restated instructions. One object, one array of findings.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/mobile-accessibility of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml
  • references/phase-1-react-native-and-expo-auditing.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Mobile Accessibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile Accessibility compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Accessibility this skillCommunity-Access/accessibility-agents422—~1.1kAutomated safety check: PassMIT
ThemingCode-with-Beto/skills141—~2.5kAutomated safety check: PassNone
Building Native UICherryHQ/cherry-studio-app4k8 repos~2.6kAutomated safety check: PassMIT
Expo Tailwind SetupCherryHQ/cherry-studio-app4k8 repos~3kAutomated safety check: PassMIT
Screenmapaleqsio/screenmap242—~7.2kAutomated safety check: PassMIT
Expo Brownfield Integrationmweinbach/agent-coworker1562 repos~900Automated safety check: NotesCustom licence

Similar skills

  • Theming

    Code-with-Beto/skills

    Scaffold a unified, cross-platform color theme system into an Expo Router app.

    141 GitHub stars~2.5k tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Building Native UI

    CherryHQ/cherry-studio-app

    Complete guide for building beautiful apps with Expo Router.

    4k GitHub starsUsed in 8 repos~2.6k tokens
    MobileAuto-check passed
  • Expo Tailwind Setup

    CherryHQ/cherry-studio-app

    Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

    4k GitHub starsUsed in 8 repos~3k tokens
    MobileAuto-check passed
  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    242 GitHub stars~7.2k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Expo Brownfield Integration

    mweinbach/agent-coworker

    Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.

    156 GitHub starsUsed in 2 repos~900 tokens
    MobileAuto-check: notes
  • Expo UI

    arcboxlabs/linkcode

    Framework (OSS). An agent skill from arcboxlabs/linkcode.

    156 GitHub stars~1.2k tokensUpdated 10 days ago
    MobileAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    422 GitHub stars~1.2k tokensUpdated 14 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~1.2k tokensUpdated 14 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~932 tokensUpdated 14 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    422 GitHub stars~1.5k tokensUpdated 14 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    422 GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    422 GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

Questions about Mobile Accessibility

What does Mobile Accessibility do?

React Native, Expo, iOS and Android: labels, roles and touch targets. Mobile Accessibility is an agent skill from Community-Access/accessibility-agents. React Native, Expo, iOS and Android: labels, roles and touch targets.

When should I use Mobile Accessibility?

Mobile Accessibility fits situations like: tasks that involve Accessibility; tasks that involve Cross-platform mobile apps; tasks that involve Mobile UI design.

How do I install Mobile Accessibility in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill mobile-accessibility -a claude-code`. Or copy the skill folder (skills/mobile-accessibility in Community-Access/accessibility-agents) into .claude/skills/mobile-accessibility in your project. Claude Code loads it when a task matches its description.

How do I install Mobile Accessibility in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill mobile-accessibility -a codex`. Or copy the skill folder (skills/mobile-accessibility in Community-Access/accessibility-agents) into .agents/skills/mobile-accessibility in your project. Codex loads it when a task matches its description.

Can I use Mobile Accessibility in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill mobile-accessibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-accessibility, .gemini/skills/mobile-accessibility, .github/skills/mobile-accessibility and .opencode/skills/mobile-accessibility in your project.

What does Mobile Accessibility need to run?

Going by SKILL.md and its folder, Mobile Accessibility needs the command-line tools its instructions call (adb).

Does Mobile Accessibility access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mobile Accessibility safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mobile Accessibility use?

Mobile Accessibility is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile Accessibility use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.

What are the alternatives to Mobile Accessibility?

Skills that share tags, products or a category with Mobile Accessibility: Theming (Code-with-Beto/skills, 141 stars), Building Native UI (CherryHQ/cherry-studio-app, 4k stars), Expo Tailwind Setup (CherryHQ/cherry-studio-app, 4k stars) and Screenmap (aleqsio/screenmap, 242 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Accessibility?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.