Rules

Link to Rules 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. 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

important

The Color Contrast rule uses a trained computer vision algorithm. This type of rule will only show results from views rendered on the screen at the time of the scan.

	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.	WCAG 2.0 - 4.1.2 A	Critical
CheckBox Name	CheckBox Name Any CheckBox element should have an accessible name available for assistive technologies such as TalkBack and Voice Access.	WCAG 2.0 - 1.3.1 A	Serious
Color Contrast	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.	WCAG 2.0 - 1.4.3 AA	Serious
Edit Text Name	Edit Text Name Text input elements should have an accessible name available for assistive technologies such as TalkBack and Voice Access.	WCAG 2.0 - 1.3.1 A	Serious
Edit Text Value	Edit Text Value Text input elements should have its value available for assistive technologies such as TalkBack and Voice Access.	WCAG 2.0 - 4.1.2 A	Critical
Focusable Text	Focusable Text Views containing text should be focusable for assistive technologies such as TalkBack.	WCAG 2.0 - 1.3.2 A	Critical
Hidden Active View Focus	Hidden Active View Focus Interactive views should not be covered by another view, either entirely or partially.	WCAG 2.0 - 2.4.3 A	Critical
Hidden Informative View Focus	Hidden Informative View Focus Views containing information should not be covered by another view, either entirely or partially.	WCAG 2.0 - 1.3.2 A	Critical
ImageView Name	ImageView Name Focusable image elements should provide a meaningful accessible name available for assistive technologies such as TalkBack and Voice Access.	WCAG 2.0 - 1.1.1 A	Critical
Inactive Accessible View	Inactive Accessible View Interactive views should be focusable with assistive technology.	WCAG 2.0 - 4.1.2 A	Critical
Label In Name	Label In Name An accessibility focusable view should ensure its name is included in its visible label.	WCAG 2.1 - 2.5.3 A	Serious
Nested Active Control	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.	WCAG 2.0 - 2.1.1 A	Critical
Nested Element Name	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.	WCAG 2.0 - 1.3.2 A	Critical
Screen Title	Screen Title Every screen within an application should provide a title to be announced by assistive technology.	WCAG 2.0 - 2.4.2 A	Moderate
Switch Name	Switch Name Any Switch element should have an accessible name available for assistive technologies such as TalkBack and Voice Access.	WCAG 2.0 - 1.3.1 A	Critical
Touch Target Size	Touch Target Size All active controls should have a minimum of 44dp by 44dp visual and tappable area.	WCAG 2.1 - 2.5.5 AAA	Moderate
Touch Target Spacing	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.	WCAG 2.2 - 2.5.8 AA	Moderate

Rules

Rule Overview

Is this page helpful?

Help us improve this page

Still need help?