Accessibility issue - keyboard focus ignoring buttons on layers
To comply with Accessibility requirements, I've been testing whether my course is fully functional when using only a keyboard. Unfortunately, I've found that it is not.
On most slides, the keyboard focus works great using the TAB key to move the focus and the ENTER key to make selections. If I'm on a base layer of a slide which has on-screen buttons, and I use the TAB key to move the keyboard focus (the yellow square) between the available on-screen buttons, this works fine. I can tab through to the last available button at the bottom of the screen, then, if I TAB again, it returns to the first available on-screen button again at the top of the slide and moves through the buttons all over again. This is the expected behaviour.
However, if I am on a slide layer (not the base layer) which has on-screen buttons, the keyboard focus moves between the available on-screen buttons until it gets to the last button on the screen. But, if I click the TAB button again, expecting it to focus again at the first available on-screen button and start again, it does not. Instead, it focuses on the Storyline player buttons only - ignoring all of the on-screen buttons - and then loops continuously...
For a user who can only access the course via a screen reader, I imagine this would be even more frustrating, as the computer keeps repeating: MENU TAB - NOTES TAB - MENU TAB - NOTES TAB - MENU TAB - NOTES TAB etc, when all they want to do is access the on-screen buttons that the course is telling them to click! I believe this issue is very concerning, as users with a disability should be given the same access to the course as users who are able to use a mouse and/or able to hear the narration without a screen reader.
I've submitted this case to the Storyline Support team and they've been able to replicate this, but do not have a workaround at this stage. They have reported it to the QA Team to look into further.
In the meantime, I was wondering if anyone else out there had encountered this issue, and if so, if you have worked out a way to avoid this from happening?