krutikJain/android-compose-accessibility
skills/android-compose-accessibility/SKILL.md
Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
$ install --global
skillsauthnpx skillsauth add krutikJain/android-agent-skills android-compose-accessibilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 12:32 PM184.1s6 files scanned
SKILL.md
- name:
- android-compose-accessibility
- description:
- Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
- version:
- 0.1.0
- category:
- ui
- tags:
- ["android", "compose", "accessibility", "a11y"]
- include:
- ["compose accessibility review", "android semantics issue compose", "focus order in compose", "screen reader compose ui", "large font compose problem"]
- exclude:
- ["dependency conflict only", "room schema only", "gradle plugin migration only"]
- owners:
- ["@android-agent-skills/maintainers"]
- test_targets:
- ["examples/orbittasks-compose", "examples/orbittasks-xml", "benchmarks/triggers.jsonl"]
Android Compose Accessibility
When To Use
- Use this skill when the request is about: compose accessibility review, android semantics issue compose, focus order in compose.
- Primary outcome: Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
- Handoff skills when the scope expands:
android-ui-states-validationandroid-testing-ui
Workflow
- Identify whether the target surface is Compose, View system, or a mixed interoperability screen.
- Select the lowest-friction UI pattern that satisfies responsiveness, accessibility, and performance needs.
- Build the UI around stable state, explicit side effects, and reusable design tokens.
- Exercise edge cases such as long text, font scaling, RTL, and narrow devices in the fixture apps.
- Validate with unit, UI, and screenshot-friendly checks before handing off.
Guardrails
- Optimize for stable state and predictable rendering before adding animation or abstraction.
- Respect accessibility semantics, contrast, focus order, and touch target guidance by default.
- Do not mix Compose and View system ownership without an explicit interoperability boundary.
- Prefer measured performance work over premature micro-optimizations.
Anti-Patterns
- Embedding navigation or business logic directly in leaf UI components.
- Using fixed dimensions that break on localization or dynamic text.
- Ignoring semantics and announcing only visual changes.
- Porting XML patterns directly into Compose without adapting the mental model.
Examples
Happy path
- Scenario: Add semantics and readable labels to the Compose OrbitTasks cards.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:connectedDebugAndroidTest
Edge case
- Scenario: Validate font scaling, contrast, and touch targets in narrow layouts.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:assembleDebug
Failure recovery
- Scenario: Differentiate accessibility requests from general UI validation or theme work.
- Command:
python3 scripts/eval_triggers.py --skill android-compose-accessibility
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
- https://developer.android.com/develop/ui/compose/accessibility
- https://developer.android.com/guide/topics/ui/accessibility/apps
- https://developer.android.com/guide/topics/ui/accessibility/testing
- https://developer.android.com/develop/ui/compose/layouts/adaptive
Related Skills
krutikJain/android-testing-ui
testing
VerifiedTrustedCommunity
Validate Android UI behavior with Compose UI tests, Espresso-style checks, screenshot assertions, and accessibility verification.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-state-management
data-ai
VerifiedTrustedCommunity
Model screen state, events, reducers, and side effects for Android UIs with predictable lifecycle-aware ownership.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-serialization-offline-sync
tools
VerifiedTrustedCommunity
Coordinate serialization, caching, conflict handling, and offline-first sync flows in Android apps.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-security-best-practices
development
VerifiedTrustedCommunity
Apply Android app security guidance around secrets, storage, network trust, exported components, and least privilege.
5SKILL.mdUpdated Apr 25, 2026