Reading order in iOS VoiceOver
Reading order in iOS VoiceOver
- Subject: Reading order in iOS VoiceOver
- From: Bruno Ultisoft <email@hidden>
- Date: Wed, 10 Aug 2011 09:52:25 -0400
In iOS VoiceOver, If I have an editable text view with an accessibility label (or an html text area), it seems as if it always reads the potentially very long text it contains before ever informing the user that it's an editable text field, or whether it's dimmed, like they would in Mac VoiceOver. I understand that this allows for a certain degree of consistency between editable text views and simple text fields, but I can't help but think that the Mac implementation makes more sense. Is this a bug, or a deliberate design decision?
On a related note, is there any documentation anywhere about the order in which VoiceOver reads things (in Mac or iOS)? I have to craft an accessibility strategy for an in-house application framework, and it would be invaluable.
Thanks! _______________________________________________
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