enabling-accessibility-checks

Integrate Espresso's AccessibilityValidator into Jetpack Compose UI tests.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill enabling-accessibility-checks-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enabling-accessibility-checks
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/compose/debug/enabling-accessibility-checks
Command: npx skills add https://github.com/trancee/MeshLink-template --skill enabling-accessibility-checks-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of ensuring Jetpack Compose UI components meet accessibility standards by automating the integration of Espresso's AccessibilityValidator into the Compose testing pipeline.

Core Features & Use Cases

  • Automated Validation: Automatically runs accessibility checks before every UI-mutating action like clicks or scrolls.
  • Hybrid Support: Allows sharing a single validator instance between Espresso and Compose for consistent reporting in hybrid apps.
  • Use Case: Use this when you need to enforce touch-target and contrast compliance in your Compose-only screens to prevent accessibility regressions during CI/CD.

Quick Start

Use the enabling-accessibility-checks skill to configure your AndroidComposeTestRule to automatically validate accessibility rules before every UI interaction.

Frequently Asked Questions about enabling-accessibility-checks

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

FAQPage Schema
How do I automate accessibility checks in Jetpack Compose UI tests?

To automate accessibility checks in Jetpack Compose UI tests, integrate Espresso's AccessibilityValidator into your AndroidComposeTestRule to automatically validate touch targets, content descriptions, and contrast ratios before every UI-mutating action.

Can I run Espresso accessibility validation in a hybrid app with Compose screens?

Yes, you can run Espresso accessibility validation in a hybrid app by sharing a single AccessibilityValidator instance between Espresso and Compose, ensuring consistent accessibility compliance reporting across both UI frameworks.

What Android API level is required for reliable Compose accessibility testing?

Reliable Compose accessibility testing using Espresso's AccessibilityValidator requires real-device execution on Android API 34 or higher to accurately evaluate the Compose semantics tree during automated instrumentation tests.

How does automated accessibility validation prevent regressions in Compose screens?

Automated accessibility validation prevents regressions in Compose screens by automatically checking touch-target sizes and contrast ratios against accessibility standards before UI interactions, enforcing compliance during your CI/CD pipeline.

What elements of the Compose semantics tree are validated by Espresso's AccessibilityValidator?

Espresso's AccessibilityValidator validates the Compose semantics tree by automatically checking touch target sizes, content descriptions, and contrast ratios during instrumentation tests to ensure full accessibility compliance.

Are there limitations when enabling accessibility checks for Compose in automated testing?

Limitations when enabling accessibility checks for Compose include requiring real-device execution on API 34+ for reliable results, as standard emulators or lower API levels may not accurately validate the semantics tree.