Keyboard focus for interactive elements

• Use native controls, such as Button, EditText, CheckBox, Switch, etc. These controls are focusable by default.
• For custom controls, set the following attributes to manually define focus behavior:
  • android:focusable="true"
  • android:focusableInTouchMode="true"
  • android:importantForAccessibility="yes"
• Ensure focus can move logically between elements and is not blocked or trapped.

• Use standard UIKit or SwiftUI controls, such as UIButton, UITextField, UISwitch, etc. These controls are focusable by default.
• For custom controls:
  • Ensure the element is accessible by setting isAccessibilityElement = YES.
  • Expose proper accessibility traits, such as .button, .adjustable, etc.
• Support keyboard activation by handling:
  • UIKeyCommand in UIKit.
  • Keyboard shortcuts or focus activation in SwiftUI.
• Ensure focus can move logically between elements and is not blocked or trapped.

• Use accessible components, such as Pressable, TouchableOpacity, Button, instead of plain View.
• Set accessible={true}
• Set the correct accessibilityRole. For example, button, checkbox, link.
• Support keyboard interaction by handling onKeyPress for Enter or Space where needed.

• Use built-in widgets, such as ElevatedButton, TextField, Switch, etc. These widgets are focusable by default.
• For custom widgets:
  • Wrap them in Focus or FocusableActionDetector.
  • Ensure actions are mapped to keyboard inputs. For example, ActivateIntent.

The following Android example scan report highlights a keyboard focus for interactive elements violation for a button that is marked as important for accessibility but is not focusable.

Error

• The button has the android:importantForAccessibility attribute set to yes, but the android:focusable attribute is set to false. As a result, the button is not reachable via keyboard navigation.

Fix

To fix this violation:

• Set the android:focusable attribute to true for the button in your layout XML file to make it focusable via keyboard navigation.

The following iOS example scan report highlights a keyboard focus for interactive elements violation for a button that is marked as an accessibility element but does not respond to user interaction.

Error

• The button has the isAccessibilityElement property set to 1, or true, but the accessibilityRespondsToUserInteraction property is set to 0, or false. As a result, the button is not reachable via keyboard navigation.

Fix

To fix this violation:

• Set the accessibilityRespondsToUserInteraction property to true for the button to make it focusable via keyboard navigation.