I have to make sure our Storyline presentations are accessible. I have links to email in the presentation as text in a text box on the slide. I have triggered the text to connect to the email address and it shows as a link. However, when I publish and test with JAWS and NVDA the links are not being recognized. Has anyone else ever had this happen and how did you remedy it?
Ashley, I have a similar problem. I'm publishing Storyline presentations as SCORM objects and simple screen readers I've tried do not read my text. I hear "paragraph empty" -- I'm trying to figure out why and how I can fix it! I hope the e-Learning Heros are listening!
Hi Ashley,
Thank you for your quick reply - and thank you also for the link to the resources you provided. I'm still having trouble; but maybe my assumptions are incorrect.
If I create a text box in Storyline, I thought that screen readers would recognize that object as text and read it. That is not the case? I will have to provide Alt-Text (in this case all the text content in each text box) for every text box in my Storyline presentation? Whew. The video discusses adding alt-text to images, but doesn't address text in a text box (or a text-speech bubble as displayed in the video tutorial)
If you disabled the ability for the alt text - then it wouldn't be accessible to screen readers. You don't have to place text in there, but that option does have to be selected.
Also, what screen reader are you using? I've only ever seen/tested JAWS - and I know its a bit particular in terms of needing to be updated regularly and using an updated version of the Internet Explorer browser, as I think that's all it supports.
I think I resolved it; it was a browser issue. I use Chrome and that was what I was using to test. When I tried the same process with Internet Explorer, it worked fine. Still doing some testing though. (The screen reader keeps naming titles/subtitles & textboxes "graphics" though. Not sure where it is getting that tag/label.)
I do not have JAWS, so I downloaded NVDA - it's an open source product and although I do not have sight issues, it was quick to install and get up and running with it.
I did not intentionally disable the ALT-Text (except on items that were for visual design only) and since the screen reader seems to work OK in Internet Explorer I'm much more confident that Storyline did its job. More likely user error/ignorance for these issues.
Once again I am rescued by E-Learning Heros! Thanks so much for your diligence and rapid response!
No problem Penny - and I'm not familiar with NVDA - but if it works and you think that's what your users will be accessing it through, then definitely conduct your testing there. Also,, the "graphics" issue is something we're aware of and have reported to our QA team for review, but I don't have any additional information to share on the status of that bug. I'll add this thread to the existing report filed with our QA team so that they're aware of another user being impacted.
6 Replies
Ashley, I have a similar problem. I'm publishing Storyline presentations as SCORM objects and simple screen readers I've tried do not read my text. I hear "paragraph empty" -- I'm trying to figure out why and how I can fix it! I hope the e-Learning Heros are listening!
Hi Penny,
Have you included alt text for those options? You may also want to review the information here in regards to Storyline's 508 compliance.
Hi Ashley,
Thank you for your quick reply - and thank you also for the link to the resources you provided. I'm still having trouble; but maybe my assumptions are incorrect.
If I create a text box in Storyline, I thought that screen readers would recognize that object as text and read it. That is not the case? I will have to provide Alt-Text (in this case all the text content in each text box) for every text box in my Storyline presentation? Whew. The video discusses adding alt-text to images, but doesn't address text in a text box (or a text-speech bubble as displayed in the video tutorial)
Thanks again!
Penny
If you disabled the ability for the alt text - then it wouldn't be accessible to screen readers. You don't have to place text in there, but that option does have to be selected.
Also, what screen reader are you using? I've only ever seen/tested JAWS - and I know its a bit particular in terms of needing to be updated regularly and using an updated version of the Internet Explorer browser, as I think that's all it supports.
Hi Ashley -
I think I resolved it; it was a browser issue. I use Chrome and that was what I was using to test. When I tried the same process with Internet Explorer, it worked fine. Still doing some testing though. (The screen reader keeps naming titles/subtitles & textboxes "graphics" though. Not sure where it is getting that tag/label.)
I do not have JAWS, so I downloaded NVDA - it's an open source product and although I do not have sight issues, it was quick to install and get up and running with it.
I did not intentionally disable the ALT-Text (except on items that were for visual design only) and since the screen reader seems to work OK in Internet Explorer I'm much more confident that Storyline did its job. More likely user error/ignorance for these issues.
Once again I am rescued by E-Learning Heros! Thanks so much for your diligence and rapid response!
No problem Penny - and I'm not familiar with NVDA - but if it works and you think that's what your users will be accessing it through, then definitely conduct your testing there. Also,, the "graphics" issue is something we're aware of and have reported to our QA team for review, but I don't have any additional information to share on the status of that bug. I'll add this thread to the existing report filed with our QA team so that they're aware of another user being impacted.
This discussion is closed. You can start a new discussion or contact Articulate Support.