mobile-accessibility

mobile-accessibility is a skill for Claude Code, Codex from Community-Access/accessibility-agents. It costs 21 tokens per session (1,084 once invoked), scanned A, original, MIT.

A review guide for accessibility in React Native, iOS, and Android mobile apps. It checks screen-reader labels and roles, touch target sizes, hints, and platform-specific behavior.

In plain words
What is it for?
Use it to audit or fix a mobile screen, review React Native or native app code, check touch targets, or test screen-reader compatibility.
Why use it?
It helps identify mobile controls that are hard to hear, understand, or activate. It also separates mobile accessibility checks from web accessibility checks.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present.

Part of the accessibility-agents plugin — 108 skills, 6 hooks shipped together

Good fit Use it to audit or fix a mobile screen, review React Native or native app code, check touch targets, or test screen-reader compatibility.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/community-access/accessibility-agents/mobile-accessibility
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Community-Access/accessibility-agents --skill mobile-accessibility
Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Claude Code, Codex.

Or install accessibility-agents, the plugin that ships this one along with the rest of its 108 skills, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mobile-accessibility

README.md
[![agentmods](https://agentmods.dev/badge/skills/community-access/accessibility-agents/mobile-accessibility/github.svg)](https://agentmods.dev/skills/community-access/accessibility-agents/mobile-accessibility)
Your own site
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/mobile-accessibility/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mobile-accessibility

Your own site · 80×15
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/mobile-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,084 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 5
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • medium Agent Snooping · line 5
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01084
Opus 5.5 $0.00008 $0.00434
Sonnet 5.5 $0.00004 $0.00217
Haiku 4.5 $0.00002 $0.00108

Measured 1mo ago against content hash 53b8af05f0c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mobile-accessibility scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/mobile-accessibility/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

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:

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

React Native - Debugging:

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

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

Read the full file on GitHub · 164 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · -231 lines · -61 tokens per session 53b8af05f0c7
  2. 1mo ago First seen · 395 lines · 82 tokens per session scan A 7d78c44ae599

Subscribe to this mod's changes

mobile-accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (428 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,084 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

figma-a11y-annotations

Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…

cvs-health/ios-swiftui-accessibility-techniques · 110 tokens

iOS SwiftUI Accessibility

Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.

cvs-health/ios-swiftui-accessibility-techniques · 67 tokens

accessibility

Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…

ericrisco/rsc-harness · 86 tokens

Accessibility Auditor

Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.

PramodDutta/qaskills · 32 tokens

Accessibility A11y Enhanced

Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.

PramodDutta/qaskills · 34 tokens

accessibility-commerce

Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.

finsilabs/awesome-ecommerce-skills · 33 tokens