skills.rest
benoberkfell
benoberkfellCOMMUNITY
Explore all skills by this author →
GitHub

android-a11y-semantics

Apply Jetpack Compose semantics properties and actions for TalkBack accessibility.

Updated Aug 27, 2026
Search Tags:#accessibility#a11y#android#ui-testing#semantics#compose-semantics#talkback
One-click install
npx skills add https://github.com/benoberkfell/claude-plugins --skill android-a11y-semantics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-a11y-semantics
Source: https://github.com/benoberkfell/claude-plugins/tree/main/plugins/android-a11y/skills/android-a11y-semantics
Command: npx skills add https://github.com/benoberkfell/claude-plugins --skill android-a11y-semantics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Compose accessibility: ensure Jetpack Compose UIs are discoverable and usable by accessibility services by applying semantics properties and actions.

Core Features & Use Cases

  • Content descriptions for non-text elements to aid screen readers.
  • Roles and state descriptions to convey element purpose and status.
  • Live regions, headings, traversal, and collection semantics for richer navigation.
  • Support for actions, long-click, custom actions, and text input semantics to enable accessible interactions.

Quick Start

Add a semantics modifier to a composable and verify TalkBack announces the element.

Frequently Asked Questions about android-a11y-semantics

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

FAQPage Schema
How do I make Jetpack Compose UI elements accessible to TalkBack?▼

Make Jetpack Compose UI elements accessible by applying semantics modifiers to expose content descriptions, roles, and state. This ensures TalkBack correctly announces UI components like images and buttons during navigation.

What are Compose semantics properties used for in Android accessibility?▼

Compose semantics properties expose element purpose and status to accessibility services. They convey roles, state descriptions, and live region updates, enabling richer navigation and correct announcements for diverse layouts.

How do I add content descriptions to non-text elements in Jetpack Compose?▼

Add content descriptions to non-text Compose elements by applying the appropriate semantics modifier. This aids screen readers by providing descriptive text for visual elements like images that lack inherent text.

Can I define custom actions and traversal order with Compose semantics?▼

Yes, you can define custom actions, long-click support, and traversal order using Compose semantics. This enables accessible interactions and controls navigational behavior across collection semantics in your layout.

Does this approach support live region updates for dynamic UI changes?▼

Yes, Compose semantics support live region updates to announce dynamic UI changes. By applying the correct semantics properties, accessibility services receive notifications when content updates occur.

When should I use semantics visibility controls in Android Compose?▼

Use semantics visibility controls in Android Compose to merge or hide child elements from accessibility services. This prevents confusing announcements and ensures correct grouping of nested UI components.

Related Skills

Explore More Software Engineering Skills→
soham2008xyzsoham2008xyz

Expo UI Jetpack Compose

Build Jetpack Compose UI screens in Expo apps using @expo/ui/jetpack-compose.

Community
Intermediate
rock-hurock-hu

android-accessibility

Audit and fix Android accessibility issues in Jetpack Compose apps.

Community
Basic
eygrabereygraber
1

ui-accessibility

Enforce descriptive semantics and accessible touch targets in Jetpack Compose UI components.

Community
Intermediate
siddhantparadoxsiddhantparadox

android-accessibility

Audit Android Jetpack Compose UI components for WCAG AA accessibility compliance.

Community
Intermediate