iOS Developers + VoiceOver

Last Updated: October 30, 2011 – Added text entry and editing with VoiceOver.
By: David Law

What is the purpose of this page?

This small collection of writing serves to define the most commonly used gestures in VoiceOver, and key reasons to think about implementing VoiceOver in app development.

What are the most common gestures used in VoiceOver?

Since VoiceOver is an overlaid and interception style technology, interfacing with apps is different and not a fluid visual experience as iOS is intended. Imagine that your sole ability to navigate an iOS device or app is to follow the output of what a voice tells you is presently displayed. For many this would be hair-pulling and frustrating, but to those with visual impairments or blindness – they have little to no choice.  VoiceOver breaks down the normal visual experience into one to four finger gestures which represent either different navigation instructions or reading text and items on the screen. The following listing of VoiceOver commands and their functions are from: Settings > Accessibility > VoiceOver >  VoiceOver Practice

Swiping Gestures:

• One finger swipe right = “Move to next item.”
• One finger swipe left = “Move to previous item.”
• One finger swipe down = “Move to next item using Rotor setting”
• One finger swipe up = “Move to previous item using Rotor setting”
• Two finger swipe right = no action
• Two finger swipe left = no action
• Two finger swipe down = “Read page starting at selected item.”
• Two finger swipe up = “Read page starting at the top.”
• Three finger swipe right = “Scroll left one page.”
• Three finger swipe left = “Scroll right one page.”
• Four finger swipe right/left or up/down = no action

Rotational Gestures:

• Rotate Clockwise = “Select next Rotor setting.” (Place your fingers in the position as if turning a knob on a dial.)

• Rotate Counterclockwise = “Select previous Rotor setting.”

Pinch Gestures:

• Pinch Closed = “Unselect text.”
• Pinch Open = “Select text.”

Tapping Gestures:

• One finger tap = “Touch, select item under your finger.”
• Two finger tap = “Pause or continue speech.”
• Two finger double tap = “Start and stop the current action.”
• Two finger double tap and hold = “Set custom label.”
• Two finger triple tap = no action
• Three finger single tap =  “Speak page number or rows being displayed.”
• Three finger double tap = “Toggle speech on and off.”
• Three finger triple tap = “Toggle screen curtain on and off.”
• Four finger tap near top of screen = “Move to the first element”.
• Four finger single tap near bottom of page = “Move to the last element.”
• Four finger double tap = no action

 

Setting custom labels in iOS 5.

Within VoiceOver, using the double tap and hold function, proceeding three tones a dialogue will prompt you to change the current label or to create a new custom label.  This is extremely useful within apps that do not properly label their buttons or elements, but nevertheless the program is used a lot. Through personal experimentation however, custom labels do not carry over to new app version updates or reinstallation. Labels can be created for renaming apps, and controls within an app. One notable bug within 5.01, when attempting to re-label the Phone app all other custom labels are lost.

Text Entry and Editing using VoiceOver:

Initially working with, and getting used to, the different gestures and interaction with VoiceOver when typing can be a learning curve. Once this has been overcome however typing and editing text becomes easier and a more familiar experience.

Practice using the Search iPhone screen.

The “standard typing” mode of typing is turned on by default when using VoiceOver with text fields. This means that each letter is announced when touched and not entered into the text field until double tapped.

Switching to “touch typing” mode:

Touch typing mode is a very different experience from the standard typing mode. As each character is selected and announced, lifting your finger enters the character into the text field.

1. While within a text field, use the “rotor” gesture (placing two fingers on the screen and turning as if a dial) to begin cycling through the list of options.
2. Continue the “rotor” gesture until “typing mode” appears as an option.
3. Swipe down with one finger to enable touch typing mode. (Swipe up to re-enable standard typing mode.)

Editing text and copy/paste:

1. Use the “rotor” gesture to select either “characters” or “words” modes. In these modes, swiping up or down with one finger will select either the next or previous character or word in the text field. Unlike some screen readers which focus on the previous character or word being modified, VoiceOver announces the actual character or word as selected.
2. For making changes to multiple characters, words, or to copy and paste, select the “edit” function from the rotor menu  using a single finger swipe up or down. Once a command is chosen, either “select”, “:select all” or “paste”;  double tap the text field to open the pop-up menu of specific editing options to “cut”, “copy” or “paste”. This may seem very confusing and counter-intuitive at first. Keep practicing using the Search iPhone screen or blank document to grasp these tools before using with important correspondence or meaningful work.

Why is it important or worthwhile to develop apps with VoiceOver in mind?

While still serving a relatively small segment of the overall iOS user population, developing with VoiceOver compatibility ensures all users have a chance to see your products and services. For instance, if one of your family members or friends had vision problems and wanted to use the new app that “everyone is talking about”, they soon find it not working properly with VoiceOver and essentially useless to them. By no means direct or intentional this closes the door of their ability to use that product, service, or support that company/developer. So big deal, that is only one person or five out of tens of thousands effected right? Well, perhaps through that unfortunate experience, other non-visually impaired users learn of that person’s experience and choose to no longer support that developer/company’s releases. Or the visually impaired person themselves decides to write about or vocalize their experiences to others. Certainly not all applications or services will ever be entirely accessible. However, this should not diminish the ideal to be as user friendly as possible and provide a universal experience to all users despite their disabilities or challenges.