android-accessibility

Android Accessibility

Overview

Accessibility is not optional — it's a requirement for reaching all users. This skill covers building accessible Android UIs with Jetpack Compose semantics, proper content descriptions, touch target sizing, TalkBack compatibility, and systematic testing with Accessibility Scanner.

When to Use

• Building new UI screens or components
• Reviewing existing UI for accessibility compliance
• Fixing accessibility issues flagged by Accessibility Scanner or users
• Before shipping any user-facing feature

Skip when: Working on non-UI code (repositories, use cases, networking).

Core Standards

Requirement	Standard
Touch targets	Minimum 48dp x 48dp
Color contrast (text)	>= 4.5:1 (normal), >= 3:1 (large 18sp+)
Color contrast (UI components)	>= 3:1 against adjacent colors
Content descriptions	All meaningful visual elements
Focus order	Logical reading order
No color-only information	Additional indicators required

Core Process

Step 1: Content Descriptions

1. Every meaningful visual element needs a description:

// Icons that convey information
Icon(
    imageVector = Icons.Default.Delete,
    contentDescription = "Delete task", // Descriptive, not "delete icon"
)

// Decorative elements — explicitly null
Icon(
    imageVector = Icons.Default.Circle,
    contentDescription = null, // Decorative, TalkBack skips it
)

// Images
Image(
    painter = painterResource(R.drawable.user_avatar),
    contentDescription = "Profile photo of ${user.name}",
)

// IconButtons — the button gets the description
IconButton(
    onClick = onDelete,
) {
    Icon(
        imageVector = Icons.Default.Delete,
        contentDescription = "Delete task", // On the Icon, read by TalkBack
    )
}

1. Description rules:
   • Describe the action or meaning, not the visual appearance
   • "Delete task" not "red trash can icon"
   • "Search" not "magnifying glass"
   • Use null for purely decorative elements
   • Include dynamic content: "Profile photo of John" not just "profile photo"