android-accessibility

Audit and fix Android accessibility issues in Jetpack Compose apps.

Updated Mar 9, 2025
One-click install
npx skills add https://github.com/rock-hu/vitamin-compose --skill android-accessibility-rock-hu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-accessibility
Source: https://github.com/rock-hu/vitamin-compose/tree/main/.github/skills/android-accessibility
Command: npx skills add https://github.com/rock-hu/vitamin-compose --skill android-accessibility-rock-hu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams audit and fix Android UI accessibility issues in Jetpack Compose applications, reducing manual review time and improving user inclusivity.

Core Features & Use Cases

  • Comprehensive checklist: Provides an expert checklist for common accessibility gaps in Android Compose UIs, including content descriptions, focus order, touch targets, color contrast, and semantic grouping.
  • Prompts & guidance: Includes targeted prompts to guide developers, reviewers, and QA through accessibility verification during UI development and code review.
  • Use Case: When integrating a new screen or component, apply the checklist to ensure TalkBack compatibility and accessible navigation across the app.

Quick Start

Run the android-accessibility skill to audit the current Compose screen for content descriptions, focus order, and touch target sizes.

Frequently Asked Questions about android-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Jetpack Compose UI for Android accessibility issues?

You can audit Jetpack Compose UI for accessibility by applying a targeted checklist that verifies content descriptions, focus semantics, touch target sizes, color contrast, and semantic grouping to meet accessibility standards.

What accessibility checks should I perform for TalkBack compatibility in Android?

TalkBack compatibility checks for Android include verifying content descriptions, focus order, touch target sizes, color contrast, and proper semantic grouping to ensure screen readers can navigate the application effectively.

Can I use this to review accessibility during Android component onboarding?

Yes, you can use this checklist to review accessibility during Android component onboarding, guiding developers and QA through verification of focus semantics and content descriptions across new screens and flows.

What is the best way to fix focus order and semantic grouping in Compose?

The best way to fix focus order and semantic grouping in Compose is to apply targeted review prompts that enforce proper focus semantics and ensure correct content grouping for accessible navigation.

How do I ensure proper touch target size and color contrast in Compose?

To ensure proper touch target size and color contrast in Compose, run an accessibility audit that enforces standard checks for these visual and interactive elements to satisfy accessibility requirements.