Re: Presenting a modal view on iOS, and accessibility
Re: Presenting a modal view on iOS, and accessibility
- Subject: Re: Presenting a modal view on iOS, and accessibility
- From: Travis Siegel <email@hidden>
- Date: Wed, 11 May 2011 13:32:08 -0500
On May 11, 2011, at 1:13 PM, Jonathan del Strother wrote:
In principle I agree with you, but right now it's a horrible
experience where a VO user has no idea that a new menu has appeared,
and has to flick through all the other items on the page (it's a table
view, so it's a fairly long page) before they reach the menu buttons
that have popped up. I'm not sure how to fix that without temporarily
preventing access to the other items.
Well, not knowing what specifically your screen looks like, I can't
comment specifically, but for most of us using vo on ios devices,
there's no reason to think all vo users are going to "flick" through
all the items on the screen. I only use the flick myself for hard to
find items, such as the purchase button in the ios store, when I'm
having trouble locating it directly. For the most part, I (and most
others I know) simply move around the screen using touch and movement
to navigate the screen. Flicking right/left through *all* the items
on a page is entirely too time consuming, and I don't know about
other vo users, but I've got better things to do with my time than
spend it flicking through a hundred (or thereabouts) items on a
screen. I usually touch the screen as close to the item I can get,
then flick right/left only a few items to get to the item in
question. As for why the vo user doesn't know your menu popped up,
perhaps something needs to be done (audio cue or something) to alert
the vo user that something on screen has changed. If the menu is a
result of user interaction (I.E. user did something to make it
appear) then an audio cue that it is present shouldn't hurt).
Otherwise, it may be worth thinking about the design, and try to
figure out why the user would have no idea the menu has shown up.
Usually gui changes happen as a result of something haappening. Find
some way to make the user aware that something happened, and then
you'll have a good framework to build on as far as making users aware
there's something that needs done now.
Sorry I can't be more specific than that, and I know that non-vo
users have a hard time determining what might or might not be useful
as far as required information goes, but generally, if you can
determine how to identify the popup's purpose, the user probably can
too if they're given some sort of feedback about the event.
Hope this helps.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden