android-accessibility

new-silvermoon/awesome-android-agent-skills · updated Apr 26, 2026

$npx skills add https://github.com/new-silvermoon/awesome-android-agent-skills --skill android-accessibility
0 commentsdiscussion
summary

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

skill.md

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.761 reviews
  • Meera Jain· Dec 16, 2024

    We added android-accessibility from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Dhruvi Jain· Dec 12, 2024

    android-accessibility has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Min Khanna· Dec 12, 2024

    android-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Xiao Ramirez· Dec 8, 2024

    Useful defaults in android-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Xiao Shah· Dec 8, 2024

    Solid pick for teams standardizing on skills: android-accessibility is focused, and the summary matches what you get after install.

  • Mateo Malhotra· Dec 4, 2024

    Registry listing for android-accessibility matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Xiao Jackson· Nov 27, 2024

    android-accessibility has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Mateo Chawla· Nov 23, 2024

    android-accessibility reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Maya Anderson· Nov 7, 2024

    Keeps context tight: android-accessibility is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Oshnikdeep· Nov 3, 2024

    Solid pick for teams standardizing on skills: android-accessibility is focused, and the summary matches what you get after install.

showing 1-10 of 61

1 / 7