Greetings to everyone, we've detected many interaction problems between the storyline library and the screen readers. Very often the screen reader's navigation buttons gets "stuck" within the inherent region of the library, making the exit difficult unless the use through focus, is there any way to fix this?
I'd like to ask a few questions to help clarify your experience:
Can you clarify what you meant by Storyline 'library'? Are you referring to the menu or glossary of your course?
What screen reader are you using to test your course?
By 'stuck', do you mean the course freezes or just the accessible navigation? Does pressing the arrow keys allow you to cycle through the readable objects in the slide? For this one, kindly go through this article and let me know if any of the behavior you're experiencing is addressed.
Additionally, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
1 Reply
Hello C B,
Happy to help!
I'd like to ask a few questions to help clarify your experience:
Storyline 360: Slide Content Is More Accessible
Additionally, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!