android-accessibility

Identifies Android Jetpack Compose accessibility issues including content descriptions, touch targets, color contrast, focus management, and semantic structuring.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/devanfer02/telnetquiz --skill android-accessibility-devanfer02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-accessibility
Source: https://github.com/devanfer02/telnetquiz/tree/main/.claude/skills/android-accessibility
Command: npx skills add https://github.com/devanfer02/telnetquiz --skill android-accessibility-devanfer02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Android development teams identify and fix accessibility issues in Jetpack Compose-based user interfaces, reducing accessibility defects and improving user experience for all users.

Core Features & Use Cases

  • Automated audits: Quickly assess screens for common accessibility issues such as missing content descriptions, insufficient touch targets, and color contrast problems.
  • Semantics & navigation: Ensure proper focus order, semantic grouping, and heading semantics for screen readers.
  • Code-to-design handoff: Provide actionable guidance during UI reviews and handoffs to ensure accessibility is maintained from design to implementation.

Quick Start

Run a quick accessibility audit on a sample Jetpack Compose screen (e.g., MainScreen) and address any issues related to content descriptions, touch targets, color contrast, and focus management.

Frequently Asked Questions about android-accessibility

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

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

To audit Android accessibility in Jetpack Compose, review UI components for missing content descriptions, insufficient 48dp touch targets, WCAG color contrast failures, and improper focus management. This process identifies defects during UI audits and design-to-code handoffs.

What are common Jetpack Compose accessibility issues with contentDescription and touch targets?

Common Jetpack Compose accessibility issues include missing contentDescription properties for screen readers and touch targets smaller than 48dp. Auditing identifies these defects along with poor color contrast, improper semantic grouping, and missing heading semantics.

Does this accessibility audit check WCAG color contrast and semantic grouping?

Yes, the accessibility audit checks WCAG color contrast ratios, semantic grouping, and heading semantics. It also validates contentDescription handling, 48dp touch target sizing, and focus order management for Jetpack Compose UIs.

How do I fix screen reader focus order and heading semantics in Jetpack Compose?

Fix screen reader focus order and heading semantics in Jetpack Compose by applying proper semantic grouping and heading modifiers. An accessibility audit identifies incorrect focus management and semantic structuring to provide actionable code guidance.

Can I use this for design-to-code handoffs to ensure Android app accessibility?

Yes, you can use accessibility auditing during design-to-code handoffs for Android apps. It provides actionable guidance during UI reviews to ensure content descriptions, touch targets, and color contrast are maintained from design to Jetpack Compose implementation.