Rules

Link to Rules copied to clipboard

Learn more about the accessibility rules supported within axe DevTools for iOS. 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
  3. Best Practice - defined by Accessibility Experts at Deque

In the navigation bar under Rules & Remediation, you'll find detailed information on each rule, including resolution tips. View this guide for impact rating and descriptions. Some rules will 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

Rule & Description Guidelines Impact
Accessibility Element Focus Box

A11y Element Focus Box
Ensures a view's accessibility path, or VoiceOver focus box, encapsulates its own visual on-screen frame.

Best Practice Moderate
Active Control Name

Active Control Name
Any interactive view should have an accessible name available for assistive technologies such as VoiceOver and Voice Control.

WCAG 2.0 - 4.1.2 A Critical
Associated Text

Associated Text
A control should get its accessible name from a nearby label available for assistive technologies such as VoiceOver and Voice Control.

WCAG 2.0 - 1.3.1 A Critical or Serious
Colliding Controls

Colliding Controls
Interactive views should not have intersecting bounds.

Platform Guideline Moderate
Colliding Views

Colliding Views
Views containing information should not intersect with another view, either entirely or partially.

Platform Guideline Minor
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
Conflicting Traits

Conflicting Traits
Views should not have conflicting accessibility traits.

Platform Guideline Critical
Focusable Text

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

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 VoiceOver and Voice Control.

WCAG 2.0 - 1.1.1 A Critical
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
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
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
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
Meaningful Accessible Name

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

Platform Guideline Minor
Nested Elements Name

Nested Elements Name
A focusable view should have all visible text within its accessible name available to assistive technologies like VoiceOver and Voice Control.

WCAG 2.0 - 1.3.2 A Critical
Screen Orientation

Screen Orientation
Views should adhere to the user's preferred display orientation.

WCAG 2.1 - 1.3.4 AA Serious
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
Supports Dynamic Type

Supports Dynamic Type  Experimental Rule
Text elements should have the required properties to support Dynamic Type and resize the text to the user's device preference.

Platform Guideline Critical
Touch Target Size

Touch Target Size
All active controls should have a minimum of 44pt by 44pt 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 points or must be positioned so that if a circle with a diameter of 24 points 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