Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/mobile-accessibility/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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.
[](https://agentmods.dev/skills/community-access/accessibility-agents/mobile-accessibility)<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="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.03382 |
| Opus 5 | $0.00041 | $0.01691 |
| Sonnet 5 | $0.00016 | $0.00676 |
| Haiku 4.5 | $0.00008 | $0.00338 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 395 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 1: React Native and Expo Auditing
1.1 Core Accessibility Props
Review every interactive element for these required props:
| Prop | Required on | Purpose | WCAG Mapping |
|---|---|---|---|
accessible |
Custom touchable elements | Marks element as accessible node | 1.1.1, 4.1.2 |
accessibilityLabel |
All interactive/informational elements | Human-readable name | 1.1.1, 4.1.2 |
accessibilityRole |
Interactive elements | Communicates element type to AT | 4.1.2 |
accessibilityHint |
Elements whose purpose isn't obvious | Extra context for screen readers | 1.3.3 |
accessibilityState |
Toggles, checkboxes, expandables | Communicates current state | 4.1.2 |
accessibilityValue |
Sliders, progress bars, steppers | Communicates current value | 1.3.1, 4.1.2 |
importantForAccessibility |
Android only - hides decorative elements | Filters AT tree | 1.1.1 |
accessibilityElementsHidden |
iOS only - hides from VoiceOver | Filters AT tree | 1.1.1 |
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.
- 3d ago First seen · 395 lines · 82 tokens per session scan A 7d78c44ae599
Mobile Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 82 tokens to every session and 3,382 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
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 23 WCAG criteria.
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.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
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…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…