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:

  1. WCAG Success Criterion
  2. Platform Guideline - defined by Apple or Google
  3. 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, SwiftUI, React Native, .NET MAUI
  • Android: XML, Compose, React Native, .NET MAUI

Support for other view types are being explored. Found a bug? Checkout the known issues page for potential workarounds or let us know about it. Contact us at helpdesk@deque.com or support.deque.com.

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.

 WCAG 2.0 - 4.1.2 A Critical Android

iOS
Edit Text Value

Edit Text Value
Text input elements should have their value available for assistive technologies such as TalkBack and Voice Access.

 WCAG 2.0 - 4.1.2 A Critical Android
Focusable Text

Focusable Text
Views containing text should be focusable for assistive technologies such as VoiceOver.

 WCAG 2.0 - 1.3.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
In ScrollView

In ScrollView
Text should be within a scrollable view to ensure that all elements are visible on all screen sizes.

 WCAG 2.0 - 1.4.4 AA Serious iOS
Inaccessible Action

Inaccessible Action  Experimental Rule
An interactive view should have the ability to be activated with assistive technology.

 WCAG 2.0 - 2.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.

 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.

 WCAG 2.1 - 2.5.3 A Serious Android

iOS
Meaningful Accessible Name

Meaningful Accessible Name
An element's accessible name should not include its accessibility trait.

 Platform Guideline Minor 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.

 WCAG 2.1 - 2.5.5 AAA Moderate Android

iOS
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 Android

iOS

Is this page helpful?

Help us improve this page

Still need help?