Success Criteria:

Name Name describes the purpose of the control and matches any visible label
Role Identifies itself as a switch (Android) or switch button (iOS)
Grouping Visible label is grouped with the switch in a single swipe
State State options: disabled/dimmed, On/off
Focus Focused by swipe or touch
Actions Double tap to toggle

External Keyboard Support

tab To focus
space bar Activates on iOS and Android
enter key Activates on Android

Native Element

  • Switch or Toggle Button - A switch is a visual toggle between two mutually exclusive states — on and off
  • You should use a native switch rather than a custom element because it will announce the correct built-in screen reader announcements for free.


Name describes the purpose of the control

  • iOS Options
    • Set a label in Interface Builder in the Identity Inspector
    • Group visible text label and the control in the same view container: accessibilityFrameInContainerSpace
    • setTitle( ) method
    • If no visible label, use accessibilityLabel on control
    • Hint is used only if the results of interacting with it are not obvious from the control's label.
    • Match visible label, if any
    • To hide labels from VoiceOver announcements, uncheck the Accessibility Enabled checkbox in the Identity Inspector
    • If hiding visible label, use accessibilityLabel on control
  • Android Options
    • android:text XML attribute
    • Optional: use contentDescription for a more descriptive name, depending on type of view and for elements without a visible label.
    • contentDescription overrides android:text
    • Use labelFor attribute to connect the visible label to the control


  • iOS
    • Standard UISwitchControl
  • Android
    • Standard Switch or Toggle Button


  • Group visible label with switch
  • iOS
    • accessibilityFrame
    • accessibilityFrameInContainerSpace
    • GroupView
    • Only the container class is an accessible element
  • Android
    • ViewGroup
    • Set the container object's android:screenReaderFocusable attribute to true, and each inner object's android:focusable attribute to false. In doing so, accessibility services can present the inner elements' content descriptions/names, one after the other, in a single announcement


  • iOS
    • Active: isEnabled property
    • Disabled: UIAccessibilityTraitNotEnabled
    • on/off: isOn or setOn
    • Announcement: on/off
  • Android
    • Active: android:enabled=true
    • Disabled: android:enabled=false
    • on/off: isChecked, setChecked, toggle
    • Announcement: on/off


Only manage focus when needed. Primarily, let the device manage default focus.

Consider how focus should be managed between child elements and their parent views.

    • iOS Options
      • accessibilityElementIsFocused
      • isAccessibilityElement - Yes, if the element can respond to user input
      • To move screen reader focus to newly revealed content: UIAccessibilityLayoutChangedNotification
      • To NOT move focus, but announce new content: UIAccessibilityAnnouncementNotification
    • Android Options
      • android:focusable=true
      • android=clickable=true
      • Implement an onClick( ) event handler for keyboard, not onTouch( )
      • nextFocusDown
      • nextFocusUp
      • nextFocusRight
      • nextFocusLeft
      • accessibilityTraversalBefore (or after)
      • To move screen reader focus to newly revealed content: Type_View_Focused
      • To NOT move focus, but announce new content: accessibilityLiveRegion
      • To hide controls: Important_For _Accessibility_NO


  • iOS
    • To toggle: double tap
  • Android
    • To toggle: double tap