android-accessibility

Audit Android Jetpack Compose UI for accessibility issues and WCAG AA compliance.

10.4k|519|Updated Apr 15, 2023
One-click install
npx skills add https://github.com/maxrave-dev/SimpMusic --skill android-accessibility-maxrave-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-accessibility
Source: https://github.com/maxrave-dev/SimpMusic/tree/main/.claude/skills/android-accessibility
Command: npx skills add https://github.com/maxrave-dev/SimpMusic --skill android-accessibility-maxrave-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers ensure their Android applications are accessible to users with disabilities by providing a comprehensive checklist and guidance for identifying and fixing accessibility issues, particularly within Jetpack Compose UI.

Core Features & Use Cases

  • Accessibility Auditing: Provides a structured checklist covering content descriptions, touch target sizes, color contrast, focus order, and semantic grouping.
  • Jetpack Compose Focus: Offers specific advice tailored for accessibility in modern Android UI development with Compose.
  • Use Case: A developer can use this Skill to audit a new feature built with Jetpack Compose, ensuring all interactive elements have proper content descriptions and sufficient touch target sizes before release.

Quick Start

Review the provided Android UI code snippet for content description and touch target size issues.

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?

Auditing Android accessibility in Jetpack Compose involves checking interactive elements and text for proper content descriptions, adequate touch target sizes, sufficient color contrast, logical focus order, and correct semantic grouping to meet WCAG AA standards.

What is the best way to fix screen reader navigation for Android UI elements?

The best way to fix screen reader navigation is by applying proper content descriptions and semantic grouping to interactive elements, ensuring a logical focus order that allows screen readers to traverse the Android UI effectively.

Does this accessibility checklist support WCAG AA standards for Android apps?

Yes, the accessibility guidance ensures compliance with WCAG AA standards by auditing Android UI components for adequate color contrast, touch target sizes, and content descriptions required for compliance.

How do I ensure sufficient touch target size and color contrast in Android UI development?

You ensure sufficient touch target size and color contrast by auditing your Jetpack Compose UI elements against accessibility guidelines, verifying that interactive components meet minimum size requirements and color contrast ratios.

When should I use semantic grouping for Jetpack Compose interactive elements?

You should use semantic grouping for Jetpack Compose interactive elements when multiple components form a single logical action, ensuring screen readers announce them as one cohesive unit rather than separate fragmented items.