android-a11y-testing

Validate Jetpack Compose Android UI accessibility with TalkBack and Espresso checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/benoberkfell/claude-plugins --skill android-a11y-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-a11y-testing
Source: https://github.com/benoberkfell/claude-plugins/tree/main/plugins/android-a11y/skills/android-a11y-testing
Command: npx skills add https://github.com/benoberkfell/claude-plugins --skill android-a11y-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Help developers verify that their Jetpack Compose UIs are accessible, by guiding manual TalkBack checks, automated scanners, and semantics-based UI tests.

Core Features & Use Cases

  • Manual Accessibility Testing: Step-by-step TalkBack enablement and gesture checks to ensure elements are reachable and descriptions are meaningful.
  • Automated Scanning & Semantics Testing: Use UI test matchers and assertions to validate roles, content descriptions, states, and actions.
  • Integration Testing Recipes: Example code for Espresso Accessibility checks and ATF integration to catch a11y regressions.

Quick Start

Run the included accessibility test recipes to validate your Compose UI's a11y behavior.

Frequently Asked Questions about android-a11y-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Jetpack Compose UI for accessibility defects?

Automate Compose accessibility testing by using UI test matchers and Espresso accessibility checks to assert semantic roles, content descriptions, and state announcements in your integration pipeline.

How do I validate TalkBack navigation and semantic descriptions in Android?

Validate TalkBack navigation by performing step-by-step gesture checks to ensure UI elements are reachable, then use Compose semantics matchers to assert meaningful descriptions and roles are present.

Can I integrate Espresso accessibility checks into my Compose UI testing pipeline?

Yes, you can integrate Espresso accessibility checks and ATF into your integration test pipelines to automatically catch a11y regressions alongside your standard Compose UI tests.

What do I need to know to write automated a11y tests for Android UIs?

Writing automated a11y tests requires knowledge of Compose semantics, test rules, and common accessibility patterns to properly validate roles, descriptions, and state announcements.

What's the best way to assert live region behavior and state announcements in Compose?

Assert live region behavior and state announcements by applying Compose semantics test rules and matchers to verify that dynamic content changes trigger the correct accessibility announcements.