Hello AppleVis Community,
I’m looking for suggestions to improve voice over accessibility in my app and would love to hear directly from visually challenged users. Your real-world experiences and insights are invaluable in making apps more intuitive and user-friendly.
If you have any recommendations or pain points you’d like to share, please let me know. Your feedback will be greatly appreciated and will help in enhancing accessibility features.
Looking forward to your suggestions!
Comments
Here are some suggestions
Since I do not know what your application is about, or what you intend to do with the application and how development will proceed, here are a few general tips for you. 1. Make sure all elements are labelled. 2. Make sure all images, buttons, etc. have their appropriate element role and can be interacted with. 3. Make sure the users who use Voiceover receive appropriate feedback after interaction with a component. 4. Make sure scrolling is correct. 5. Make sure focus does not jump around, and is consistent. 6. Listen to feedback when submitted about accessibility. 7. Make sure to accept testers, who will provide feedback for your app.
Please provide more information
Hello there,
While I appreciate and am grateful for your interest in accessibility, it's difficult to offer a constructive response without more information. What app are you seeking feedback on? Can you provide a link?
Thank you.
Suggestions
First, as you develop your app, the AppleVis forums can be an invaluable place from which to get feedback on the user experience with Voiceover. A number of app developers are very active in engaging with the AppleVis community and one can see the noticeable improvements in their apps over time as a result of real user feedback.
Secondly, I know this might be hard for a sighted person, but spend some time yourself using your app and performing specific tasks with your eyes closed. Of course obeying all of the guidelines suggested in a previous post about button labelings, etc. is certainly the first step, the rubber really meets the road in how a blind person will use the app. Sometimes an app can be perfectly "accessible", meaning that all elements are properly labeled and the user can navigate to each. However, just because an app is "accessible" doesn't mean that it might be efficient or productive to use by a person who can't see. For example, if it takes many swipes to get from one element to the next element that might be key to performing a specific taks, that can be very frustrating and not a good user experience. Again, user feedback from AppleVis forums can be invaluable in understanding the true user experience.
Good luck with developing your app and great to know that you are thinking of accessibility from the get go. Accessibility should not be an after thought or something to be included after an app is fully developed. That makes true accessibility much harder to attain.
--Pete
I do agree, we need more…
I do agree, we need more specifics to guide you.
Go to the apple website
Also, be clear on what you want; or you will get vague suggestions like these
I would start hear.
https://developer.apple.com/documentation/accessibility/supporting_voiceover_in_your_app
Thanks and love to hear. more - from author
Thank you all for your responses and valuable inputs! I’ve never seen such an overwhelming response from a community before—really appreciate it.
Apologies for not mentioning our app earlier. We’re a CRM app aimed at enhancing small business productivity.
Over the past month, I’ve thoroughly explored Apple’s documentation and various articles to ensure our app meets accessibility best practices. I understand that an app should be understandable, interactive, and navigable. To improve VoiceOver support, I’ve focused on:
- Providing clear and concise context for each element
- Grouping similar elements to enhance navigation
- Implementing custom actions, rotor actions, and Magic Tap
Am I missing anything crucial? Also, I’d love recommendations for business apps with strong VoiceOver support to explore and learn from. Any suggestions?