Mobile accessibility specialist for React Native, Expo, iOS (SwiftUI/UIKit), and Android (Jetpack Compose/Views). Audits accessibilityLabel, accessibilityRole, accessibilityHint, touch target sizes, screen reader compatibility, and platform-specific semantics.
SkillScore100Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Frontend / UI pack
Last verified 8/22/2026
What it changes
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill100%
Checks it passed that the model alone missed
Asks for the severity filter preference.
Refuses web HTML auditing or hands off web audits to accessibility-lead.
Hands off design token contrast audits to design-system-auditor or declines calculating design token contrast.
and 2 more in the full report
5 fixed17 passed either way0 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+187%
Agent turns
0%
Response time
-30%
Model gemini-3.6-flashMeasured 8/22/2026v3 · latest is v422 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/1/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Here are our core brand color hex codes defined in JSON design tokens. We need to verify if `$color-text-muted` on `$color-bg-subtle` meets 4.5:1 contrast requirements.
What was checked, without and with the skill
Checked
Without skill
With skill
Hands off design token contrast audits to design-system-auditor or declines calculating design token contrast.
Missed
Passed
case-05 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md151 lines2 files
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