Android Accessibility

new-silvermoon/awesome-android-agent-skills/.github/skills/ui/android-accessibility

by new-silvermoon82900eacc8dbe13de93c6310af27b9df4b2bd2f6No licenseListed Oct 9, 2026Updated Oct 9, 2026

Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.

Instructions onlySoftware Development
AI-generated overview

Checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.

What it does
Provides an accessibility review checklist covering content descriptions, touch target size, color contrast, focus and semantics, and headings. It also supplies example prompts an agent can use to inspect a given component or screen. The output is audit guidance and suggested fixes rather than generated code or files.
When to use it
Use it when reviewing an Android UI component or screen for accessibility problems. It is aimed at Jetpack Compose code, including images, icons, buttons, custom toggles, and heading structure.
Requirements
No scripts or tools are bundled; it is instructions only. Applying the guidance assumes access to the Android or Jetpack Compose source being reviewed.

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?"

Source and attribution

Source:new-silvermoon/awesome-android-agent-skillsin.github/skills/ui/android-accessibilityat commit82900ea

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal