android-a11y-patterns

Apply reusable accessibility patterns to Jetpack Compose UI components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides reusable accessibility patterns to improve Jetpack Compose UI accessibility.

Core Features & Use Cases

  • Predefined patterns for accessible clickable elements, cards, lists, dialogs, and forms to ensure correct semantics and inclusive interactions.
  • Guidance on applying content descriptions, roles, and semantics to real-world Compose UI components.
  • Use Case: Imagine building a data-driven list where each row announces its state clearly to screen readers and supports keyboard navigation.

Quick Start

Run the android-a11y-patterns guide to apply accessible patterns to your Compose UI components.

Frequently Asked Questions about android-a11y-patterns

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

FAQPage Schema
How do I make Jetpack Compose UI components accessible to screen readers?

To make Jetpack Compose UI accessible, you apply specific semantics, content descriptions, and roles to clickable elements, cards, lists, dialogs, and forms using predefined patterns for consistent inclusive interactions.

What is the best way to add semantics to clickable elements and cards in Compose?

The best way to add semantics to Compose clickable elements and cards is by applying predefined accessibility patterns that ensure correct roles and content descriptions are announced clearly to assistive technologies.

How do I ensure my Compose list rows announce their state correctly for accessibility?

You ensure Compose list rows announce their state correctly by applying accessibility patterns that configure semantics for each row, enabling clear screen reader announcements and supporting keyboard navigation.

Do I need to manually configure semantics for every Compose dialog and form?

You do not need to manually configure semantics for every Compose dialog and form from scratch; you can use predefined accessibility patterns to ensure correct semantics and inclusive interactions across these components.

What accessibility patterns are available for Compose UI components?

Available accessibility patterns for Compose UI cover clickable elements, cards, lists, dialogs, and forms, providing guidance on applying content descriptions, roles, and semantics to ensure consistent accessible interfaces.

Can I use these accessibility patterns for both Compose forms and dialogs?

Yes, you can use these accessibility patterns for both Compose forms and dialogs, as the patterns are designed to apply correct semantics and inclusive interactions across these specific UI components.