android-a11y-hybrid-debugging

Diagnose accessibility issues in hybrid View/Compose apps using ADB workflows and layout inspection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging hybrid View/Compose accessibility issues across mixed UI scenarios, including focus management between ComposeView and legacy Views, WebView accessibility challenges, and end-to-end ADB-based diagnostics.

Core Features & Use Cases

  • Interoperability guidelines for ComposeView and AndroidView to ensure a stable accessibility tree and consistent focus behavior.
  • WebView accessibility setup and debugging techniques to surface DOM semantics to TalkBack and related services.
  • ADB-driven debugging workflows, layout inspector usage, and semantics tree analysis to diagnose traversal order and content descriptions in hybrid screens.

Quick Start

Run the guide against a hybrid screen to diagnose and fix focus, WebView, and ADB accessibility issues.

Frequently Asked Questions about android-a11y-hybrid-debugging

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

FAQPage Schema
How do I debug accessibility focus issues in a hybrid View and Compose app?

Debug hybrid View and Compose accessibility by applying interop guidelines for ComposeView and AndroidView to stabilize the accessibility tree and ensure consistent focus behavior across mixed UI components.

What's the best way to surface WebView DOM semantics to TalkBack in a Compose app?

Surface WebView DOM semantics to TalkBack by applying WebView accessibility setup and debugging techniques that bridge web content semantics to Android's native accessibility services within hybrid screens.

How do I use ADB to diagnose traversal order and content descriptions in Android screens?

Diagnose traversal order and content descriptions using ADB-driven debugging workflows and semantics tree analysis to inspect hybrid screens and verify focus handling and semantics coordination.

Does this approach work with RecyclerView containing ComposeView?

Yes, hybrid View and Compose accessibility debugging covers mixed UI scenarios like RecyclerView with ComposeView, providing diagnostics and lifecycle strategies to maintain a stable accessibility tree.

Why does focus management break between ComposeView and legacy Views?

Focus management breaks between ComposeView and legacy Views due to semantics coordination and lifecycle mismatches, which you can fix by applying interop delegation strategies and stable accessibility tree guidelines.