Rules

Link to Rules copied to clipboard

Learn more about the accessibility rules supported within axe DevTools for Appium.

Below you'll find brief descriptions of each rule along with the link to the original guidelines. Rules come from three sources:

WCAG Success Criterion
Platform Guideline - defined by Apple or Google
Best Practice - defined by Accessibility Experts at Deque

Within the table below, you'll find a link to the corresponding rule on iOS or Android for more detailed information including resolution tips. View this guide for impact rating and descriptions. Some rules may be marked with an experimental badge. Learn more about experimental rules and how you can help improve them.

tip

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

Rule Overview

Rules have been developed and tested in the below platform and view configurations:

iOS: UIKit, React Native, .NET MAUI
Android: XML, React Native, .NET MAUI

Support for other view types are being actively worked on and will be a part of an upcoming release.

	Rule & Description	Guidelines	Impact	Platform Remediation
Active Control/View Name	Active Control/View Name Any interactive view should have an accessible name available for assistive technologies such as VoiceOver and Voice Control for iOS, or TalkBack and Voice Access for Android. This rule runs on `button` elements and will be expanded to other interactive types in an upcoming release.	WCAG 2.0 - 4.1.2 A	Critical	Android iOS
ImageView Name	ImageView Name Focusable image elements should provide a meaningful accessible name available for assistive technologies such as VoiceOver and Voice Control for iOS, or TalkBack and Voice Access for Android.	WCAG 2.0 - 1.1.1 A	Critical	Android iOS
Label At Front	Label At Front Any visible text of an interactive view should be at the start of the view's accessible name. This rule runs on `button` elements and will be expanded to other interactive types in an upcoming release.	WCAG 2.1 - 2.5.3 Best Practice	Minor	Android iOS
Label In Name	Label In Name An accessibility focusable view should ensure its name contains its visible label. This rule runs on `button` elements and will be expanded to other interactive types in an upcoming release.	WCAG 2.1 - 2.5.3 A	Serious	Android iOS
Touch Target Size	Touch Target Size All active controls should have a minimum of 44pt by 44pt in iOS, or 44dp by 44dp in Android, visual and tappable area. This rule runs on `button` elements and will be expanded to other interactive types in an upcoming release.	WCAG 2.1 - 2.5.5 AAA	Moderate	Android iOS

Rules

Rule Overview

Is this page helpful?

Help us improve this page

Try axe DevTools® Mobile SDKs

Still need help?