-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several issues with screen reader accessibility #267
Comments
To explain the issues experienced with DiceCloud Character Builder, until the user clicks once into the Right Pane solely contains the string "Magic items considered priceless don't" After clicking in the right pane, the left and right side compete for focus and occasionally reset position returning back to Top-Left and starting over before the page is fully read. The stat numbers are duplicated within screen readers, in some cases presenting 4 times in the case of the "Hit Dice" section. Sections like "Inventory" and "Spells" breaks fields that would otherwise appear to a normal person to be a contiguous sentence into multiple parts that need selected independently and the screen readers do not interpret them as continuations of sentences but instead as different columns of text. There are a limited number of fields that are simply labeled as "Image" or "Unlabeled Button" that are inaccessible. On a cursory glance, these appear to go to the same places as text links beside them, however this is a reasonably large app, so it's hard to say for sure without a more detailed review. As a suggestion for what a blind or vision impaired person would experience when using your application, if you have a recent macOS or iOS device, Apple has a feature called VoiceControl that will present the VoiceOver prompts visually over screen elements. It isn't directly transferrable as it is intended for low mobility users rather than low vision users, but it ties into the same metadata so you can get close and validate that the labels, content, and positions are correct. |
This also highlights the importance of a good keyboard-only interface for users with other disabilities or constraints. |
To tack onto this a bit - better semantic labelling of elements would make it dead-easy to build a beyond20-style translator for syncing dicecloud to roll20, foundryVTT, etc.. Big possibilities for curb-cut effects here. |
Blind and visually impaired users use screen readers like JAWS, NVDA or VoiceOver to navigate the web and other apps. These tools depend on semantic information in web apps, and on appropriate image descriptions and alternative labels.
As it is, multiple graphical buttons are read out as "unlabelled button," the tabbing order isn't streamlined and pop up windows don't capture focus.
The text was updated successfully, but these errors were encountered: