Rules for Compose Layouts

Link to Rules for Compose Layouts copied to clipboard

Learn more about the accessibility rules supported within axe DevTools for Android. Below you'll find brief descriptions of each rule along with the link to the original guidelines. Rules come from two sources:

  1. WCAG Success Criterion
  2. Best Practice - defined by Accessibility Experts at Deque

In the navigation bar under Rules & Remediation for Compose Layouts, you'll find detailed information on each rule, including resolution tips. View this guide for impact rating and descriptions.

important

Throughout our rules documentation, you'll find references to Name, Role, and Value. Please refer to WCAG's definitions.

Rule Overview

Rule & Description Guidelines Impact
Text Button Name

Text Button Name
Text Button Name looks for buttons with a click action and ensures the view is focusable and its name or text is available to TalkBack.

 WCAG 2.0 - 4.1.2 A Critical
Text Field Label

Text Field Label
Input fields require instructions provided for understanding and operating content.

 WCAG 2.0 - 1.3.1 A Serious
Icon Button Name

Icon Button Name
Icon Button Name looks for buttons with a click action and ensures the view is focusable and its name or text is available to TalkBack.

 WCAG 2.0 - 4.1.2 A Critical
Inactive Accessible View

Inactive Accessible View
Clickable Compose Views with meaningful information should not be marked as invisibleToUser.

 WCAG 2.0 - 4.1.2 A Critical
Label In Name

Label In Name
A view's name should be included or equal to its label.

 WCAG 2.1 - 2.5.3 A Moderate
Text Field Label In Name

Text Field Label In Name
A TextField's name should be included or equal to its label.

 WCAG 2.1 - 2.5.3 A Serious

Is this page helpful?

Help us improve this page

Still need help?