´óÏó´«Ã½

« Previous | Main | Next »

Google touchscreen phone goes 'eyes-free'

Post categories:

Gids | 17:15 UK time, Tuesday, 7 April 2009

It's a subject we've touched on before on our blog. How can blind and visually impaired people access the latest touchscreen phones that don't have buttons you can feel? Engineers at Google have been showing off their novel solution to the problem.

In a series of new videos, TV Raman, Google's blind technologist demonstrates the technique on the Google G1 smartphone. It's all based on relative positioning, put your finger anywhere on the screen and that becomes the 5 at the centre of the dial pad, then you can simply push up for a 2 or right for a 6 for example. There's also voice feedback and a reassuring click sound to confirm your selection.

But enough explaining, I'm sure you want to see it in action...

The question is will blind and partially sighted people really want to give up their trusty touchpads for this new system? Emma from the Ouch team, who currently uses a Nokia phone with a screenreader, says she'd only switch if there was a touchscreen phone she really wanted, but with these devices increasing in popularity it's unlikely Google's work will be in vain.

Check out more videos of their work in progress on the YouTube channel.

Comments

  • Comment number 1.

    Wow that is pretty cool. Creative solution to a potentially difficult problem.

  • Comment number 2.

    How about a far easier one, just put small raised dimples around the edge of the screen that can be used as guides.

  • Comment number 3.

    The other lovely access aspect of the G1 (I have one) is that the screen slides up to reveal the keyboard, which has a standard QWERTY keyboard with actual separate keys that you can feel, and raised bumps on the F and the J, and better still, they *click* when you press them - not a computer generated beep, but the actual buttons, you feel and hear them press.

Ìý

´óÏó´«Ã½ iD

´óÏó´«Ã½ navigation

´óÏó´«Ã½ © 2014 The ´óÏó´«Ã½ is not responsible for the content of external sites. Read more.

This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so.