Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
new-silvermoon avatar

Android Accessibility

  • 411 installs
  • 910 repo stars
  • Updated July 27, 2026
  • new-silvermoon/awesome-android-agent-skills

android-accessibility is a Claude Code skill that implements TalkBack-friendly labels, focus order, contrast, and semantic roles in Android screens so apps meet accessibility standards and remain usable for assistive tec

About

android-accessibility is an awesome-android-agent-skills checklist skill for auditing and fixing Android accessibility, especially in Jetpack Compose. The skill analyzes components for meaningful contentDescription on Image and Icon composables, decorative null descriptions, actionable labels that describe actions not icons, minimum touch target sizes, focus order, contrast, and semantic roles for TalkBack users. Developers reach for android-accessibility during pre-release review of Compose screens or when fixing accessibility bugs reported by QA or assistive technology testers. It outputs concrete remediation guidance per checklist category rather than generic WCAG theory. The skill targets Kotlin Compose UI code in Android Studio agent workflows.

  • TalkBack and semantic property usage
  • Focus order and keyboard navigation
  • Content descriptions and state announcements
  • Touch target and contrast guidance
  • Accessibility testing on device or emulator

Android Accessibility by the numbers

  • 411 all-time installs (skills.sh)
  • +16 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #332 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/new-silvermoon/awesome-android-agent-skills --skill android-accessibility

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs411
repo stars910
Last updatedJuly 27, 2026
Repositorynew-silvermoon/awesome-android-agent-skills

How do you fix Android TalkBack accessibility in Jetpack Compose?

Implement TalkBack-friendly labels, focus order, contrast, and semantic roles in Android screens so apps meet accessibility standards and remain usable for assistive technology users.

Who is it for?

Android developers shipping Jetpack Compose apps who need a structured TalkBack and assistive technology accessibility audit checklist.

Skip if: iOS VoiceOver work, web WCAG audits, or backend APIs with no Android UI surface.

When should I use this skill?

A developer asks to audit or fix Android accessibility, TalkBack labels, Compose contentDescription, touch target size, or focus order issues.

What you get

Accessibility audit findings and Compose fixes for contentDescription, touch targets, focus order, contrast, and semantic roles.

  • accessibility audit report
  • Compose remediation patches

By the numbers

  • Covers 4 core Compose accessibility checklist categories including content descriptions and touch target size

Files

SKILL.mdMarkdownGitHub ↗

Android Accessibility Checklist

Instructions

Analyze the provided component or screen for the following accessibility aspects.

1. Content Descriptions

  • Check: Do Image and Icon composables have a meaningful contentDescription?
  • Decorative: If an image is purely decorative, use contentDescription = null.
  • Actionable: If an element is clickable, the description should describe the action (e.g., "Play music"), not the icon (e.g., "Triangle").

2. Touch Target Size

  • Standard: Minimum 48x48dp for all interactive elements.
  • Fix: Use MinTouchTargetSize or wrap in Box with appropriate padding if the visual icon is smaller.

3. Color Contrast

  • Standard: WCAG AA requires 4.5:1 for normal text and 3.0:1 for large text/icons.
  • Tool: Verify colors against backgrounds using contrast logic.

4. Focus & Semantics

  • Focus Order: Ensure keyboard/screen-reader focus moves logically (e.g., Top-Start to Bottom-End).
  • Grouping: Use Modifier.semantics(mergeDescendants = true) for complex items (like a row with text and icon) so they are announced as a single item.
  • State descriptions: Use stateDescription to describe custom states (e.g., "Selected", "Checked") if standard semantics aren't enough.

5. Headings

  • Traversal: Mark title texts with Modifier.semantics { heading() } to allow screen reader users to jump between sections.

Example Prompts for Agent Usage

  • "Analyze the content description of this Image. Is it appropriate?"
  • "Check if the touch target size of this button is at least 48dp."
  • "Does this custom toggle button report its 'Checked' state to TalkBack?"

Related skills

FAQ

What does android-accessibility check in Compose?

android-accessibility checks Jetpack Compose screens for contentDescription on images and icons, decorative null labels, actionable descriptions, touch target sizes, focus order, contrast, and semantic roles.

Should decorative Compose images have contentDescription?

android-accessibility specifies decorative Compose images should use contentDescription null, while actionable elements need descriptions that explain the action, not the icon shape.

Does android-accessibility cover web accessibility?

android-accessibility focuses on Android Jetpack Compose UI and TalkBack assistive technology, not web WCAG or iOS VoiceOver implementations.

Mobile Developmentfrontendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.