Forum Discussion
Embedded Storyline accessibility issues
Hoping you might be able to help - when I embed a storyline interaction into my rise 360 courses it seems that screen readers aren't able to pick up any of the text. I've tried turning the 'accessible text' function on but it doesn't make any difference and I've tried two different screen readers with no success. I feel like I must be missing something obvious... any help is very appreciated!
7 Replies
Hi ShannonWalshe-8,
Thanks for reaching out!
Could you please share what screen readers you've used so far?
I tried replicating this behavior on my end when using NVDA and noticed I needed to use the UP and DOWN arrow keys in order to have text read aloud from the Storyline course. Here's a quick Peek.
Feel free to share a screen recording of what you are experiencing if you are still running into trouble.
Looking forward to hearing from you!
Hello, LucianaPiazza following up on this b/c we are experiencing this issue as well. I had someone test our training and they responded with this (using NVDA):
The sentence before the 4 boxes (this is the storyline block) reads with read aloud but the text in each of the 4 boxes does comply with read aloud and skips to bottom of the page which means I would have to search around to see what still needs to be completed instead of actually hearing the directions.
I opened on all the interaction tabs and was not able to click in the interaction to start the read aloud function.
(this was more b/c he's unfamiliar with the tools we use and was trying to help solve the issue):
Are these interactions pictures? If they are pictures, then accompanying alt text need to be added. If a person is using windows narrator, the tool does not function in pdfs. Read aloud is the only option. It would be more conducive to accessibility tools if the pages were not continuous, in other words possibly page breaks. What happens is that the Read aloud functions jumps back to the start of the training when it reaches the of a current page. The only way to get the current page to read is to scroll back down, then highlight the first word on that page and start the reading. When you are able to make a choice, for example, during the last lesson you can select summary or either of the other 2 buttons and the page reads from where its supposed instead of jumping back to the beginning of the training.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/reviewlet me know if you need the .story file too.
Looking forward to reading your response and helping find a solution!
