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. For more details on mobile rules, including remediation advice, please visit the axe DevTools Mobile SDK documention.
Rules come from two sources:
WCAG Success Criterion
Best Practice - defined by Accessibility Experts at Deque
tip
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
Active View Name
Active View Name
Any interactive view should have an accessible name available for assistive technologies such as TalkBack and Voice Access.
Color Contrast
Ensures that each text element has a minimum 4.5:1 contrast ratio with its background and that large text has a minimum 3.0:1 contrast ratio.
ImageView Name
Focusable image elements should provide a meaningful accessible name available for assistive technologies such as TalkBack and Voice Access.
Nested Active Control
An accessibility element should not have multiple active controls embedded within it. Each active control should be individually focused and interacted with.
Nested Element Name
A focusable view should have all visible text within its accessible name available for assistive technologies such as TalkBack and Voice Access.
Touch Target Spacing
Actionable controls should have a minimum dimension of 24 x 24 dp or must be positioned so that if a circle with a diameter of 24 dp is placed on the center of control, the circle will not intersect with another target or with the circle for another target.
