View Type in element accessibility label

Avoid including the control type name in the accessibility label of UI elements. Screen readers announce the type of UI controls based on their built-in or user-defined attributes, making the repetition of the control type in the label unnecessary and potentially verbose.

Success criteria

The rule checks for the following potential violations:

• Inclusion of control type
  Accessibility labels should not include the name of the control type (e.g., button, checkbox, text view).
• Redundant information
  Accessibility labels should focus on providing meaningful information without repeating the control type that the screen reader will automatically announce.

How to fix?

To fix violations related to view type information in accessibility labels, follow these steps:

• Remove control type information
  Ensure that the contentDescription (Android) or accessibilityLabel (iOS) does not contain the control type name. The screen reader will announce the control type automatically.
• Use descriptive labels
  Focus on providing clear and concise labels that describe the element’s purpose or content without including its type.

Example

The following example scan report highlights several elements that have accessibility labels that include the control type:

• Button labeled as test button.
• Text View labeled as textView.
• Checkbox labeled as CheckBox CheckBox.

Violation

Including the control type in the label causes redundancy and potential verbosity. For instance, a screen reader might announce “test button button”, which is repetitive and unnecessary.

Fix

• Remove button, textView, and CheckBox from the content descriptions.
• Ensure the screen reader can convey the control type automatically.