Interactive elements with unsupported type

• Set standard class names: Set the className to a standard Android widget class, such as android.widget.Button, android.widget.Switch. This ensures custom views or components expose a recognized accessibility role appropriate to the platform.
• Avoid ambiguous or undefined roles: Ensure custom interactive components do not present a generic or unsupported type like View to accessibility services.

• Set standard class names: Set the accessibilityTraits property, for example, .button, .switch, to indicate the element’s role. This ensures custom views or components expose a recognized accessibility role appropriate to the platform.
• Avoid ambiguous or undefined roles: Ensure custom interactive components do not present a generic or unsupported type like View to accessibility services.

• Set standard class names: Use the accessibilityRole prop to specify the role, such as button, switch, or link. This ensures custom views or components expose a recognized accessibility role appropriate to the platform.
• Avoid ambiguous or undefined roles
  Ensure custom interactive components do not present a generic or unsupported type like View to accessibility services.

• Set standard class names: Use the Semantics widget to define the role, such as button, checkbox, or slider. This ensures custom views or components expose a recognized accessibility role appropriate to the platform.
• Avoid ambiguous or undefined roles
  Ensure custom interactive components do not present a generic or unsupported type like View to accessibility services.

The following Android example report highlights a custom interactive element, MyCustomButton, that is exposed as an unknown widget type.

Fix

To correct this violation:

• Update the custom element to expose a supported widget type.
  In this example, set the element’s accessibility class name to android.widget.Button.

The following example scan report highlights an interactive element of type Button that does not expose a supported UIKit control class.

Fix

To correct this violation:

• Update the element to expose a supported accessibility traits using the accessibilityTraits attribute.
  In this example, set the trait to .button.