We routinely push updates to our access tools on Android; usersget these updates automatically via Android Market updates. Wejust pushed out updated versions of TalkBack, our Open Sourcescreenreader for Android, and Marvin, the Eyes-Free shell. Hereis a brief summary of these updates:

• Android applications can now programmatically discover ifTalkBack is running, thanks to the latest changes inTalkBack. From an end-user perspective, this means that you nolonger need to configure Eyes-Free shell via EyesFreeConfig tobe the default home. If you run TalkBack, and have EyesFreeShell installed, then pressing Home automatically givesyou the EyesFree Shell.Remember, you can always get to the default Android Home bylong-pressing Back.
• EyesFree Shell now includes a touch-based shortcutsmanager. Until now, shortcuts needed to be explicitly configuredby editting an XML file on the SDCard. With the recent EyesFreeupdate, you can interactively define short-cuts via a touch-basedShortCuts manager. By default, we have assigned shortcut1 to the ShortCuts manager; so to invoke this newfeature, do:
  1. Stroke left (4 using stroke dialer notation) toenter the shortcuts screen.
  2. Stroke up and to the left (1 using stroke-dialernotation) to invoke application ShortCuts Manager.
  3. Use the trackball/D-Pad to configure each of the 8 availableshortcuts.

Marvin: We hope this gives some minimal relief to the painin all the diodes on your left side.

Update To Android Access: TalkBack

Smart phones tend to be short on physical buttons --- evendevices like the G1 or MotoRola Droid have very few buttons when thephysical keyboard is not open. This provides interestingchallenges when designing an efficient eyes-free interface ---especially given the old maxim Speech is silvern, but silenceis golden!.Said differently, once you have built a systemthat talks back, the first thing you want to build is anefficient means of silencing spoken feedback.

Early versions of TalkBack on Android skimmed by without astop speech button --- you basically moved from one activity toanother,and the speech produced by the new activity effectivelystopped ongoing spoken output. However, as we make more and moreapplications work seamlessly with our Access APIs, it's alwaysbeen clear to us that we need a global stop speechgesture! Notice that I said gesture --- notkey --- stopping speech is a critical function that we'dlike to enable without having to pull out the physical keyboard,and something we'd like to have devices without a physicalkeyboard.

In the spirit of the dual to every access challenge is an opportunity toinnovate, we recently launched a new experimental TalkBackfeature on devices running Android 2.0. Devices on the Android2.0 platform have a proximity sensor on the top frontleft corner of the phone --- this is typically used to lock thescreen when you're holding the phone up to your ear when on aphone call. As the name implies, the proximitysensorfires when you get close to it --- you can activate itby waving your hand close to the top left corner of the phone. Asan experimental feature, we have configured the latest version ofTalkBack to silence ongoing speech if you wave your hand infront of the proximity sensor.

Note that this is a new, experimental feature --- it'ssomething that we welcome feedback on our public Eyes-Free GoogleGroup. We'd like to know if you accidentally activatestop speechbecause of this new feature. In having usedit for a few weeks, I find that I am not triggering itaccidentally --- but that might well be a function of how I holdthe phone.

What Devices Does This Available On?

Note that at the time of writing, the devices that have aproximity sensor that I have used this on include:

• MotoRola Droid from Verizon
• Google NexusOne

Note that the G1 and other older Android devices did not havea proximity sensor.

Video: 1Vox --- Your Query Is Our Command

Video: TalkBack And YouTube

Video: TalkBack And Google Maps