How do I install the Android Accessibility skill?

Run npx skillmds@latest add new-silvermoon/android-accessibility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Android Accessibility safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Android Accessibility?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Android Accessibility free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Android Accessibility?

new-silvermoon (@new-silvermoon) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Android Accessibility by new-silvermoon

Name: Android Accessibility
Rating: 4.666666666666667 (3 reviews)
Author: new-silvermoon

File contents

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: new-silvermoon/awesome-android-agent-skills → .github/skills/ui/android-accessibility/SKILL.md

---name: android-accessibilitydescription: Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.---# Android Accessibility Checklist## InstructionsAnalyze 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:** [`new-silvermoon/awesome-android-agent-skills`](https://github.com/new-silvermoon/awesome-android-agent-skills) → `.github/skills/ui/android-accessibility/SKILL.md`

Frequently asked questions

Android Accessibility