
Android Accessibility
- 2 installs
- 910 repo stars
- Updated July 27, 2026
- new-silvermoon/awesome-android-skills
Checklist for auditing and fixing Android accessibility issues in Jetpack Compose, covering content descriptions, touch targets, color contrast, focus order, and semantics.
About
Audits Android UI, especially Jetpack Compose, against accessibility criteria like content descriptions, 48dp touch targets, WCAG contrast, and semantic grouping. A developer uses it when reviewing or remediating accessibility for a Compose screen or component.
- Content-description rules for actionable vs decorative elements
- 48dp touch targets, WCAG contrast, and mergeDescendants semantics
Android Accessibility by the numbers
- 2 all-time installs (skills.sh)
- Ranked #942 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-skills --skill android-accessibilityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 910 |
| Last updated | July 27, 2026 |
| Repository | new-silvermoon/awesome-android-skills ↗ |
What it does
Checklist for auditing and fixing Android accessibility issues in Jetpack Compose, covering content descriptions, touch targets, color contrast, focus order, and semantics.
Files
Android Accessibility Checklist
Instructions
Analyze the provided component or screen for the following accessibility aspects.
1. Content Descriptions
- Check: Do
ImageandIconcomposables have a meaningfulcontentDescription? - 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
MinTouchTargetSizeor wrap inBoxwith 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
stateDescriptionto 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?"