[vip_students] My first experience using an accessible touch screen device
- From: "Paul J. Traynor (NCBI)" <paul.traynor@xxxxxxx>
- To: <vip_students@xxxxxxxxxxxxx>
- Date: Tue, 23 Jun 2009 14:09:26 +0100
My first experience using an accessible touch screen device
Yes, you read correctly: An accessible touch screen device! This morning, I
went to a retail store carrying mostly Apple products and had a look at the new
iPhone 3G S that was released in Germany on Friday. Apple revealed during the
WWDC keynote two weeks ago that it would have a built-in screen reader named
the same as is included in Mac OS X: VoiceOver. This is a feature not available
on the regular iPhone 3G, as its hardware capacity is insufficient.
I was not at all sure what to expect. From reading a bunch of posts on the
VIPHone Google Group, I knew that people were going through a learning curve, a
steep one at times. Up to now, something usable via a touch screen or
touch-only keys would always mean a dead-end to me and other blind people. The
iPhone 3G and the iPod Touch are not usable for me. Likewise, elevators that
have keys you only need to touch, not press, to get toa different floor, are a
real challenge. In fact I once tripped an alarm while trying to use such an
elevator, alone int he cabin and touching the emergency button accidentally.
When I arrived at the store, I had already made arrangements with them to be
allowed to take an in-depth look at the 3G S. As we went over to the iPhone
stand, one of the sales assistants already knew how to turn on VoiceOver. Apple
are documenting this in the regular iPhone user’s manual, no special docs
needed. The assistant helping me turned it on, and a clear crisp voice came out
of the built-in speakers. She was a bit confused by the changed gestures. I had
done some reading, and took over from there.
And I must say this was an amazing experience! My fingers definitely need to
get used to gestures such as flicking or tapping, or using a rotor. But having
an iPod Nano 4th generation helped with that, since moving the finger over the
screen like on a dialer felt most like tracking around the iPod’s click wheel.
Even the sound the rotor makes is the same.
Responsiveness to gestures was amazing. I own an Nokia N82, which is to date
probably the handset that reacts fastest to keyboard commands with the Talks or
MobileSpeak screen readers, but the responsiveness on the iPhone beats that by
lengths!
Finding my way around the iPhone’s UI took some getting used to. Traditional
mobile screen readers, also like most Windows or Linux screen reader solutions,
give the blind user a filtered view of the world, by default constrained to the
focus location. Only on demand can one explore the screen using mouse emulation
or similar techniques. On the iPhone, you interact with the real thing right
from the start. You touch the screen in the lower half, somewhere on the right,
and you’re told that the Safari or iPod symbol is there on the Home screen. You
move your finger to the left, and you’re told what’s right next to it. To
interact with the menu bar of the Phone app, you need to move your finger down
to the bottom and move from left to right to hear the options such as
“Contacts” or “Phone pad”. Yes, there are VoiceOver gestures to explore the
screen top to bottom, left to right. You do this by flicking left to righ
t anywhere, and the accessible controls are being walked one by one. But the
interaction model is very close to the actual screen layout most of the time.
This tremendously helped when I walked through a couple of applications with
the sales assistant standing next to me. She could literally point me to the
correct spot, and VoiceOver would speak what I needed to hear. Or she could
give me verbal directions, and my finger would find the controls.
Typing is probably going to take the most adjusting. It is nothing like typing
on the number pad of my N82. James Craig’s typing tip for VoiceOver on iPhone
helps a lot: You look for the correct key with one hand, keep your finger
there, then tap somewhere on the screen with another finger from the same or
the other hand, and the character is input. Gladly, the keyboard doesn’t change
position, and after a few letters I had a very good idea where each letter
should be, and my typing sped up within 10 typed letters already. In addition,
one can turn on word prediction/completion, which is another accessibility
feature that can also aid people with motor impairments make typing easier. It
plays nicely with VoiceOver.
This is by far not a comprehensive review or comparison. I couldn’t use many of
the features since the SIM card in that exhibited model was locked, and I don’t
have my own model yet.
Apple are speeding ahead and breaking down conventions in accessibility, or as
Mike Calvo of Serotek wrote: They’re getting to the future first. They’re the
first to include a screen reader for the blind on one of their mainstream
models. Google are going to do something similar with their G1 efforts. The API
is there, and some basic console work seems to be working already, but this is
by far not as comprehensive as what Apple are doing. RIM also have an
accessibility API, but from what I’m told, the screen reading solution that has
been hinted every now and then over the past couple of weeks is going to cost
extra money, which Apple’s solution does not. The traditional mobile
accessibility solutions on Windows Mobile and Symbian S60 all require an
additional payment of $200 to $350 for a screen reading solution, or in some
cases even proprietary hardware that then costs $2000 or even more.
And this, of course, opens up other possibilities for future implementations of
touch screen use cases, not just by Apple, but by other companies as well.
From
http://www.marcozehe.de/2009/06/22/my-first-experience-using-an-accessible-touch-screen-device/
--
I am using the free version of SPAMfighter.
We are a community of 6 million users fighting spam.
SPAMfighter has removed 80 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len
The Professional version does not have this message
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
Other related posts:
- » [vip_students] My first experience using an accessible touch screen device - Paul J. Traynor (NCBI)
