Forum Discussion
Embedded Storyline accessibility issues
I'm happy to check this for you!
We'll need to check your project file to see how the focus order is set up and how it responds to different screen readers. Would you be willing to share a copy of your project file here or privately by opening a support case for testing? We'll delete it when we're done!
I also wanted to share the following articles on accessibility to give you an idea of how Storyline 360 and screen readers interact:
- 4 Things To Know About Storyline 360 Courses and Screen Readers
- Accessible E-Learning & Screen Readers: What You Need to Know
- Storyline 360: How to Design an Accessible Course
Looking forward to hearing from you!
JoseTansengco here is the review 30 link: https://360.articulate.com/review/content/ecb7fb2b-9080-41f5-9b41-d5d2c20be56b/review
I had to use test data for privacy and compliance restrictions. I kept the same interactions that we were having issues with. I included 4 bullets from the learner that he was having difficulty with.
Our workaround for timing constraints was just to include a text only option in the accordian. Not sure if it's just to simply include instructions on how to use the screen reader (i.e. up/down arrows vs tabs) for the best experience.
Also, here is the storyline: https://360.articulate.com/review/content/9361170d-7165-4acb-993b-527501fb1af1/review
let me know if you need the .story file too.
Looking forward to reading your response and helping find a solution!
Hello emmalynewilloug,
Thanks for sharing a link to your published output!
Here are my observations when I used NVDA to read through your course (first link):
- NVDA was able to read the text inside the interaction boxes. In the highlighted example, NVDA read the text in one go, reading "Second Topic Interaction" first, followed by a brief pause, then "Select anywhere in this box to learn more <dot> button". Are you hearing something else when using NVDA and the tab key to navigate to these interactive blocks in the embedded Storyline 360 course?
- If you're referring to the interaction in the screenshot, did you try using the space bar to open the interaction? If this is not the interaction you were referring to, would you mind sharing a screenshot of the interaction that you were unable to click?
- Regarding the comments from your accessibility reviewer, were they sharing feedback that the interactions didn't work in the exported PDFs of the courses? If so, please let them know that this is the expected behavior, as the exported PDFs of the courses are used to visually share a preview of the course. Rise 360 courses can also be broken down into lessons, so they aren't one long course, giving learners breaks in between lessons.
Looking forward to your response!
Good Morning and thank you for the quick response! I'm glad to know this interaction worked, b/c we did follow all the steps for making both RISE and Storyline accessible.
I included the person sharing feedback bullets in this example training and his overall experience. He was, in fact, viewing the RISE experience as you did, not the PDF version. He mentioned that when he opened each of the interactions (the screenshots you shared above), he was not able to use the read-aloud function within each box. Instead, it jumps back to the start of the page.
Since you didn't experience any issues, could you share your process of using the screen reader? I assumed that since my person uses the screen reader for his job, he is a super user. But since training isn't done every day in his workload, maybe it's just a matter of including instructions in the training on how to use the screen reader to interact with the RISE/Storyline training.Hello emmalynewilloug,
Thank you for following up with us! I'm glad you've created your course with accessibility in mind.
The article my colleague Jose shared includes helpful resources for screen reader testing and a QA checklist that your colleague may find useful. Since you're using NVDA, here’s a webinar that walks through NVDA with Storyline, along with an article on how Rise 360 works with screen readers.
Let us know if you have any other questions!
- NVDA was able to read the text inside the interaction boxes. In the highlighted example, NVDA read the text in one go, reading "Second Topic Interaction" first, followed by a brief pause, then "Select anywhere in this box to learn more <dot> button". Are you hearing something else when using NVDA and the tab key to navigate to these interactive blocks in the embedded Storyline 360 course?
