accessibility

Audit Android UI accessibility across Jetpack Compose and views.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill accessibility-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/android-dev/skills/accessibility
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill accessibility-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android UI often fails to meet accessibility standards, making apps hard to use for users with disabilities. This skill provides a structured checklist and prompts to identify and fix common accessibility gaps in Jetpack Compose and classic Android views.

Core Features & Use Cases

  • Checklist-driven prompts cover content descriptions, focus management, touch target sizing, color contrast, and semantics.
  • Guides design reviews, QA checks, and automated checks during development to surface actionable accessibility improvements.
  • Use Case: A developer analyzes a screen to surface fixes that improve screen-reader support and keyboard navigation.

Quick Start

Run the accessibility audit across an Android screen using the provided prompts to identify the top three accessibility fixes.

Frequently Asked Questions about accessibility

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

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

Android UI accessibility audits evaluate Jetpack Compose screens using a checklist to identify focus order, semantic annotations, content descriptions, contrast, and touch target issues. This surfaces actionable improvements for screen-reader readiness.

What are the most common Android accessibility issues to check during a design review?

Common Android accessibility issues include missing content descriptions, improper focus management, insufficient color contrast, and undersized touch targets. A structured checklist surfaces these gaps across screens and components.

Does this accessibility audit work with traditional Android views or only Jetpack Compose?

This accessibility audit works with both Jetpack Compose and traditional Android views. It evaluates semantics, focus order, and screen-reader readiness across screens, components, and interactions in both UI approaches.

How do I fix screen-reader and keyboard navigation issues in an Android app?

Fix screen-reader and keyboard navigation issues by analyzing your Android screen to surface actionable improvements like adjusting focus order, adding content descriptions, and verifying semantic annotations for assistive technologies.

What is the best way to check touch target sizing and color contrast for Android components?

The best way to check touch targets and color contrast is using a checklist-driven audit that evaluates Android UI components against accessibility standards, ensuring targets are large enough and contrast meets requirements.