Hello, all,
Today, there are many apps in the AppleVis directory (for example: Dawncaster, Ranger Legend, at least half the Blindfold games, Cyber Quest, and more), that are listed as fully accessible with VoiceOver. However, Braille is a part of VoiceOver, and apps like this, which use the Unity game engine, are not fully accessible to Braille display users. In fact, the Unity engine uses an accessibility plugin with its own screen reader, and only borrows the system speech settings, making it sound like VoiceOver when it isn't. So, these apps are “accessible” without the use of VoiceOver, while being nearly unusable to people who primarily use Braille.
Because of this, people have wasted time and money on apps that do not work for us, a problem which the directory is supposed to mitigate.
I have a few ideas on how to fix this:
For users:
• When adding an app to the iOS and iPadOS directory that you know uses the Unity engine, rate the app as fully accessible without the use of VoiceOver, and/or add an accessibility comment saying that the app is Unity-based.
• If you have tested an app you entered with a Braille display, give a quick summary in the accessibility comments. For example: "Worked well with a Braille display," or "Very poor Braille display navigation."
Site Changes:
All of these suggestions don't need to be implemented, but I would appreciate it if the site admins would consider one or two of them.
• Add a field to the new app entry form, similar to the one that asks whether there is an Apple Watch app. It would ask whether the app supports Braille displays, with options for Yes, No, and Don't Know.
• Add tags or comments to pre-existing Unity app entries, indicating that they have little to no Braille display support.
• Potentially more difficult: Allow community members to flag apps as not controllable via Braille displays.
• Add a new field to the Accessibility section (near the button labeling and page elements), which allows users who know what the Unity engine is to indicate whether the app does or does not use it.
What are your thoughts on this? Does anyone have any other potential fixes, either for the AppleVis directory, or for using Unity-based apps with a Braille Display?
Thanks for reading, and have a great day!
Comments
I support this
While I am not a heavy Braille user, I definitely support this idea. ✊😆
Support
I definitely support this. Technically, the apps should be noted as working fine without the use of VoiceOver, because they do not use VoiceOver.
Adding a Question About Braille Display Support
Hi Kelly,
Thank you as always for your feedback. Based on your suggestions, we plan to update our App Directories to better incorporate braille support into the questions we ask users to complete when submitting apps. To help keep things as simple as possible, we will likely only add one additional question (as well as removing fields that are no longer relevant). I will post an update once this has been completed.
@Michael Hansen
Thank you very much! I appreciate everything the AppleVis team has done to make this a helpful and inclusive community.
One question about braille support will be fantastic. I wouldn't want to overwhelm people submitting new app entries with every question I listed in the original post. Those were just some sample questions to start the conversation.
For app entries created before the additional question is added, or entries submitted by people who are unable to test Braille support, would it be possible for community members to add the missing information? That would probably be a bigger project for the AppleVis team, so I understand if not, but it would be a useful option.
Thanks again for listening!
Considering a Yes/No Question for Now
Hi Kelly,
At the moment, we are considering a question that asks something like, "Have you tested this app with a braille display?" Users will have the option to either select 'yes' or 'no'. It is our hope that users would choose to provide additional details about braille in their accessibility comments.