How to read Accessibility Scanner results
Accessibility Scanner looks for the following opportunities to improve your app's accessibility.Content labeling
Many user interface controls depend on visual cues to indicate their meaning and use. A user with impaired vision might have difficulty seeing these cues.
You can make user interface controls more accessible with content labels. Content labels don't appear on the screen, but users with visual impairments can access them through accessibility services like TalkBack or other screen readers.
Accessibility Scanner looks for the following content labeling opportunities:
- Item label missing
Viewsthat a screen reader could focus and that have an empty spoken description, either for the
Viewsin its sub-hierarchy. Learn more about content labels.
- Item labeled with type or state
Identify cases where a
Viewhas a redundant description. Learn more about items labeled with type or state.
- Duplicate item descriptions
Identify cases where a hierarchy contains
Viewswith exactly duplicate descriptions. For example, two separately focusable buttons with descriptions of "More options" could confuse a user. Learn more about duplicate descriptions.
Accessibility Scanner examines
View hierarchies and identifies instances where users with motor impairments might have difficulty interacting with a layout.
- Clickable links
Identify uses of
UrlSpans. Learn more about clickable links.
- Duplicate clickable
Viewsthat share the same on-screen location as other clickable
Views. Learn more about duplicate clickable
- Editable item label
TextViewsthat have a non-empty
contentDescription. Learn more about editable
- Unsupported item type
Identify item types that are not supported by accessibility services. Learn more about unsupported item types.
- Traversal order
Identify possible issues in the traversal ordering of items, which might affect users of screen readers or other accessibility services. Learn more about traversal order.
Accessibility Scanner looks for small touch targets that could cause difficulty for users with motor impairments.
- Touch target size
Identify clickable and long-clickable
Viewsthat are smaller than 48x48dp in either dimension, or 32x32dp for
Viewswithin input method windows or against the display edge. You can change the minimum size in your Scanner settings. Learn more about touch target size.
Accessibility Scanner suggests improvements to color contrast ratios to make your app more accessible to visually impaired users.
- Text and image contrast
Identify text or images with a contrast ratio lower than 3.0 between the text color and background color (for non-empty
TextViews) or between the foreground and background color (for
ImageViews). You can change the minimum ratio in your Scanner settings. Learn more about color contrast.
More accessibility best practices
Read more in the Android Developer Accessibility documentation.