New shortcuts not completely accessible
Dec 28, 2020
Kudos to the design team for the great enhancements in the Dec. 15th update. The key command to list all the key commands (Shift+?) (https://articulate.com/support/article/Storyline-360-Accessible-Player-Controls) "opens" a dialog with a close "X" in the corner. In dialogs such as this, a) they need to be able to be closed with the Escape (Esc) key (which doesn't seem to work), and b) the close buttons needs to be accessible via the keyboard. It seems that you can tab to both the button to enable keyboard shortcuts and the close "X" button, but a) you can't SEE that you've tabbed to it. (Edit: I see yellow boxes now -- they aren't "over" the buttons correctly and are much too light -- make them thick and dashed and bright, please, see attachment) b) The close button is not labeled -- it just reads as "button" so you don't hear what it does when you're using a screen reader.
The information in the dialog is in a table. I suggest you make the first column headings as well as the first row, so if someone navigates in the 2nd column straight down, they can hear what the action for that shortcut is.
You might find the information here to be useful: https://www.w3.org/TR/wai-aria-practices-1.1/#dialog_modal
Additionally, the keyboard command to list commands (Shift + ?) doesn't work when NVDA is running (I tested in Firefox and in Chrome). The shortcut to replay the slide (Alt+Ctrl+r) doesn't work when JAWS is running in Firefox (it works in Chrome).
5 Replies
Hi Karin,
Thanks for reaching out and sharing your feedback! As a quick test, I published a slide to Review 360 and tested the popup menu in NVDA using Chrome.
The (Shift+?) worked for me, but I'm curious if you're using a Mac laptop as I found that (command+Shift+?) was consistent in displaying the popup with no issues.
Right now, you can use that same command again to close out the popup as described in the article mentioned:
Also, once I tabbed into the Keyboard Shortcuts menu to read the information, I found that NVDA will read through the entire table unless I used the down arrow to read through each item individually. I was informed of both the column and row with each keypress.
I appreciate you taking the time to share these helpful thoughts. I'll be sure to share your feedback and kudos with our team as we continue to improve these accessibility features!
Thanks for your reply. I'm using a PC, although I am using a Mac external
keyboard. I tried Shift + ? on my laptop (PC laptop) keyboard directly and
it didn't work. You are right that Shift+Windows+? works, as does
Shift+Command+?. Perhaps these should be included in the list of key
commands?
My comment about the Esc key is directly from the WCAG 2.0/2.1
accessibility standards. It's an expected keyboard behavior that the Esc
key closes dialogs. It would be marked as a compliance issue in an
accessibility review. FYI
RE reading through the table: When you have NVDA running, in the table,
press Ctrl+Alt+arrow keys. This is using the table reading mode/layer and
functions differently than just pressing down arrow. In particular, it will
read the cell designated as the heading cell. The first row is a heading
row, but I was suggesting making the first column a heading column, also.
If you read down the 2nd column using Ctrl+Alt+down arrow, you will not
hear the value in the first column (but you would if it was a heading
column).
Karin
Hello Karin!
Thank you for these details! I want to reach out to our team to offer additional information about the setup of the keyboard shortcuts and the keyboard shortcuts when it comes to navigating a table with NVDA.
I'll update this discussion with more details!
Hi Karin!
I wanted to thank you again for providing these details regarding the escape key and it's purpose when it comes to accessibility. This feature to close the list of keyboard shortcuts with the escape key is a part of our accessibility journey and will be added to Storyline 360. Currently, learners can close the shortcuts screen by pressing Shift+? or by tabbing to the X and pressing Enter. We'll update this discussion when we have an exact timeline.
I appreciate you sharing your findings regarding tables as well! We know tables aren't fully accessible yet, and we're continually prioritizing our accessibility roadmap. I'll pass your suggestions to our product team and update this discussion when more info is available.
This post was removed by the author