Accessibility Scanner results

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
  Identify Views that a screen reader could focus and that have an empty spoken description, either for the View or relevant Views in its sub-hierarchy. Learn more about content labels.
• Item labeled with type or state
  Identify cases where a View has a redundant description. Learn more about items labeled with type or state.
• Duplicate item descriptions
  Identify cases where a hierarchy contains Views with exactly duplicate descriptions. For example, two separately focusable buttons with descriptions of "More options" could confuse a user. Learn more about duplicate descriptions.
• Link purpose unclear
  Identify uninformative link text, such as "click here." Learn more about unclear link text.
• Unexposed text
  Identify Views with visible labels that aren't spoken by screen readers. Learn more about unexposed text.

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 ClickableSpan that aren't UrlSpans. Learn more about clickable links.
• Duplicate clickable elements
  Identify clickable elements that share the same on-screen location as other clickable elements. Learn more about duplicate clickable elements.
• Editable item label
  Identify EditTexts and editable TextViews that have a non-empty contentDescription. Learn more about editable View labels.
• 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.
• Text scaling
  Identify possible issues with font size and layout specifications when you design a user interface that may cause text to become cropped, cut, or hidden. Learn more about text scaling.

Accessibility Scanner looks for small touch targets that could cause difficulty for users with motor impairments.

• Touch target size
  Identify clickable and long-clickable Views that are smaller than 48x48dp in either dimension, or 32x32dp for Views within input method windows or against the display edge. You can change the minimum size in your Accessibility 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 Accessibility Scanner settings. Learn more about color contrast.