AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Android Accessibility

skill-prasad-vennam-awesome-android-ai-agent-skills-android-accessibility · by prasad-vennam

Use when improving app accessibility, ensuring WCAG compliance, or fixing TalkBack navigation for Android.

No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-prasad-vennam-awesome-android-ai-agent-skills-android-accessibility

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-prasad-vennam-awesome-android-ai-agent-skills-android-accessibility)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Android Accessibility? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Android Accessibility Excellence ♿🛡️

Standard practices for creating inclusive, easy-to-use Android applications that comply with WCAG 2.1+ standards.

⚡ When to Use

  • Accessibility Audit: Reviewing current UI for screen reader issues.
  • Compose Semantics: Customizing how UI elements are announced.
  • Contrast Ratios: Ensuring text is readable for low-vision users.
  • Screen Reader Support: Optimizing navigation with TalkBack.
  • Touch Target Sizes: Ensuring buttons and links are easy to hit.

🏗️ The 4 Principles (POUR)

  1. Perceivable: Users can perceive all info via sight, sound, or touch.
  2. Operable: Users can interact with the app via various methods.
  3. Understandable: UI and navigation are predictable.
  4. Robust: Compatible with many assistive tools.

🛠️ Compose Semantics Essentials

1. contentDescription

  • Rule: Every Image, IconButton, or clickable decorative icon MUST have a descriptive contentDescription.
  • Bad: contentDescription = "icon" or null for meaningful icons.
  • Good: contentDescription = "Search for products" or contentDescription = null for purely decorative items.

2. Semantic Properties

  • Use Modifier.semantics { ... } for custom descriptions or element roles.
  • Use Modifier.clearAndSetSemantics { ... } to hide complex child hierarchies from screen readers.

3. Merging Descendants

  • For a list item, use Modifier.semantics(mergeDescendants = true) to announce the whole item at once.

``kotlin Row(modifier = Modifier.semantics(mergeDescendants = true).clickable { ... }) { Text("Order #123") Text("Status: Shipped") } ``

📐 Design Best Practices

  • Contrast: Aim for 4.5:1 for normal text and 3:1 for large text.
  • Touch Targets: Minimum size of 48dp x 48dp.
  • Dynamic Type: Ensure layouts resize correctly for large font scales (@PreviewFontScales).

🧪 Testing and Verification

  • Accessibility Scanner: Use the Google app to automatically scan screens for common issues.
  • TalkBack: Manually test with the screen reader enabled on a physical device.
  • Lint Checks: Enable @LintRule for missing contentDescription.

📜 Checklist for Developers

  • [ ] Descriptive Labels: All actionable items state their purpose (e.g., "Delete Comment" vs "Delete").
  • [ ] State Announcements: Use liveRegion or AnnounceAccessibilityEvent for dynamic updates (e.g., "Added to cart").
  • [ ] Navigation Order: Ensure focus moves in a logical left-to-right, top-to-bottom order.
  • [ ] Role Identification: Mark elements as buttons, checkboxes, or headers.

🔗 Related Resources

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.