Mobile Accessibility Guidelines - Focus

Alternative input methods must


Alternative input methods must be supported.


Some users do not use the input control provided with a device, such as the touch screen, or mouse. Instead, they may use a switch device, keyboard or braille display.

All alternative methods of input and navigation that work with the platform must be supported to facilitate the needs of the user.

Interactive content must not rely on a single input method. For example, a carousel must not support only touch interaction, it must also support alternative inputs via visible .


iOS

Make sure that all focusable, active, and actionable elements are provided with the isAccessibilityElement property, set to a value of true.

Be aware that support for alternative inputs differs across mobile operating systems. For example, in iOS, interactive components are generally only focusable with an external Bluetooth keyboard when a user activates VoiceOver.

iOS Example (Objective-C)

[myButton.setIsAccessibilityElement:YES];

Android

Make sure that all focusable, active, and actionable elements are provided with the focusable attribute, set to a value of true.

Android Pass Example

<EditText
android:id="@+id/firstname"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:inputType="text"
android:focusable="true" />

HTML

Make sure that any functionality that is triggered through specific gestures such as swiping can also be triggered using a different input device, such as an external keyboard.

For example, if swiping left and right changes panels within a carousel, provide separate button controls marked 鈥淧revious鈥 and 鈥淣ext鈥 so that users who do not or cannot use swipe gestures (but who use a separate input device, such as a keyboard) can also take advantage of this functionality.

HTML Pass Example

A carousel that supports swiping left and right touch events such as touchstart, touchend, and touchmove can supplement these gestures with keyboard access using buttons, or by watching key presses:

<a href="...">Previous</a>

<a href="...">Next </a>

Testing

Procedures

  1. Activate a screen reader and physical keyboard.
  2. Identify the active screen objects, elements, and controls.
  3. Ensure that all items can be navigated to via alternative input methods.
  4. Ensure that the items can be activated via alternative input methods.
  5. Activate the item.
  6. For items with complex functionality, check for equivalent methods of action support such the arrow keys to instead of swipe up and down gestures to move a slider.

Outcome

The following checks are all true:

  • Objects, elements, and controls can be navigated to via alternative input methods;
  • Items can be activated and manipulated via alternative input methods.