Blind and Visually Impaired Community
↑
7
↓
Questions for VoiceOver users on iOS (self.Blind)
submitted by Ambitious_Toe_5267
Hello,
I am an iOS developer currently developing an app with a big focus on accessibility, and I had some questions for how VoiceOver users prefer to use it when navigating an app.
1. How often do you find yourself using the rotor feature?
2. If an app has an acronym, how would you expect VoiceOver to read out this acronym?
3. What are the most important things an app can do to improve the experience using VoiceOver?
4. What is the best app for VoiceOver you've used?
I would really appreciate any answers to this post and thanks for taking the time to read!
I am an iOS developer currently developing an app with a big focus on accessibility, and I had some questions for how VoiceOver users prefer to use it when navigating an app.
1. How often do you find yourself using the rotor feature?
2. If an app has an acronym, how would you expect VoiceOver to read out this acronym?
3. What are the most important things an app can do to improve the experience using VoiceOver?
4. What is the best app for VoiceOver you've used?
I would really appreciate any answers to this post and thanks for taking the time to read!
Marconius 7 points 2y ago
I use the rotor all the time. If you have functions that can be abstracted into rotor actions, by all means please build that into whatever you are creating.
For the rest of your questions, please read this: $1
If you make an app following those guidelines, you'll provide an inclusive experience for all users. Learn how to provide accessibility labels, values, traits, and hints, and what the differences between them are. Understand that the screen reader experience is highly linear, so work that into your user flows. Call out context changes when necessary. Use page titles and screen headings. Don't create flows that cause unexpected cursor traps. Hide decorative images and spacers; describe informative graphics if you have images of text. Watch your color contrast with text and interface components. Ensure your app functions with Dynamic Type.
All that being said, don't go overboard with hints or bend over backwards and assume an overly helpful interface. Keep things simple, clear, and concise, and follow the Apple's recommendations.
For the rest of your questions, please read this: $1
If you make an app following those guidelines, you'll provide an inclusive experience for all users. Learn how to provide accessibility labels, values, traits, and hints, and what the differences between them are. Understand that the screen reader experience is highly linear, so work that into your user flows. Call out context changes when necessary. Use page titles and screen headings. Don't create flows that cause unexpected cursor traps. Hide decorative images and spacers; describe informative graphics if you have images of text. Watch your color contrast with text and interface components. Ensure your app functions with Dynamic Type.
All that being said, don't go overboard with hints or bend over backwards and assume an overly helpful interface. Keep things simple, clear, and concise, and follow the Apple's recommendations.
Ambitious_Toe_5267 [OP] 1 points 2y ago
Thanks so much for your response!
ojjohndoe 6 points 2y ago
1. I personally use the rotor quite often.
2. Acronyms are usually pronounce as words except for when pronouncing it as a word would make no sense in which case it should be read letter by letter.
3. Please make sure your buttons actually read what they are instead of just saying button. This might sound simple but you’d be surprised how many apps are designed to wear when you place your finger on the buttons they just read aloud that it’s a button instead of telling you what it does.
2. Acronyms are usually pronounce as words except for when pronouncing it as a word would make no sense in which case it should be read letter by letter.
3. Please make sure your buttons actually read what they are instead of just saying button. This might sound simple but you’d be surprised how many apps are designed to wear when you place your finger on the buttons they just read aloud that it’s a button instead of telling you what it does.
Ambitious_Toe_5267 [OP] 1 points 2y ago
Thanks for the response!
If an app were to be displaying information such as acronyms and serial numbers, where numbers and letters are together, would you expect VoiceOver to read it as a word always and in the cases where it sounds off, you would use rotor?
If an app were to be displaying information such as acronyms and serial numbers, where numbers and letters are together, would you expect VoiceOver to read it as a word always and in the cases where it sounds off, you would use rotor?
Prefect316 1 points 2y ago
In the case of a serial number, the VO user would typically use the rotor, yes. At least in my case, I would navigate the rotor until I heard "Characters," at which point I would read the serial number character by character.
siriuslylupin6 1 points 2y ago
1. Quite often many many times a day.
2.it reads out stuff as best as it could. It sounds it out some words do sound funny.
3. Being accessible complying with the apple accessibility. App working with voice over fully.it doesn’t jump around or won’t click on things is bad.unlabled buttons is a bit lighter but stil bad.
4. there’s many dystopia is pretty good, apple’s apps are really good. Some others.messenger is not bad facebook.... not so much.
2.it reads out stuff as best as it could. It sounds it out some words do sound funny.
3. Being accessible complying with the apple accessibility. App working with voice over fully.it doesn’t jump around or won’t click on things is bad.unlabled buttons is a bit lighter but stil bad.
4. there’s many dystopia is pretty good, apple’s apps are really good. Some others.messenger is not bad facebook.... not so much.
Laser_Lens_4 1 points 2y ago
U/Marconius has the best answer.
1. A lot. It’s a pretty integral part of Voiceover.
2. Phonetically, unless it can’t be pronounced that way.
3. Follow Apple’s accessibility guidelines.
4. Dystopia for Reddit.
1. A lot. It’s a pretty integral part of Voiceover.
2. Phonetically, unless it can’t be pronounced that way.
3. Follow Apple’s accessibility guidelines.
4. Dystopia for Reddit.
Ambitious_Toe_5267 [OP] 1 points 2y ago
Could you give an example of how an acronym couldn't be pronounced phonetically? Thanks for the response by the way.
Laser_Lens_4 1 points 2y ago
I might be using the wrong word. Basically, if you have an acronym that can't be read as a word. Something like PNG. I think there's a word for those, but I can't remember.
Marconius 1 points 2y ago
If you have an initialism like IBM where the letters are pronounced individually, or an acronym where it's pronounced like a word such as NASA, it's a general a11y best practice to fully write out what that abbreviation stands for the first time a user encounters it, or at least provide an easy link to a glossary. VoiceOver will generally pronounce initialisms and acronyms correctly, but always test your implementation and listen to how VO reads out your text labels or copy.
Also, be wary of roman numerals. The Alex voice loves to read out things like "XL" as "fortieth" since it wants to be all smart and ends up making life difficult for us devs, especially when trying to use that letter grouping to say "Extra Large."
Also, be wary of roman numerals. The Alex voice loves to read out things like "XL" as "fortieth" since it wants to be all smart and ends up making life difficult for us devs, especially when trying to use that letter grouping to say "Extra Large."
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc • HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.