I am using Storyline 360 and the latest Jaws 18. I have a project with many slides in which I have ordered the tabs properly. Everything seems to be working as it should, however, each time I click the next button to load the following slide, Jaws reader reads the project name. Every single time. Is there a way to eliminate this? I've tried several things so far and nothing seems to work. The tab order has my image listed first (which is what I want), but it keeps reading the project name first no matter what I do. Help please!
It's going to read through all the items on the slide, including the project title. You can look at skipping elements of the player as detailed here. Take a look at the steps here to get started!
Is there information on this for Storyline 360? I see this info is for Storyline 2 and only works with Flash. What a about a Flash with HTML5 fallback?
Hey Cody! The method in the article Ashley shared also works in Storyline 360. Flash/HTML Fallback should work--you can check out the supported browsers in our documentation on Storyline 360 Accessibility in Published Courses.
I am having this issue, as well. JAWS reads the filename at the beginning of every slide. When I press the space bar to skip player navigation, it skips most of the navigation but still goes to the PREV and NEXT buttons, which is good - I want it to do that, but it also reads the filename each time it goes to a new slide. In addition, when it goes to the new slide, the "NEXT" button is highlighted but pressing the space bar does not activate it (it just reads "space") until you use the tab key again to go to the slide items in the tab order and then back to the PREV and NEXT buttons.
Is it reading the file name, the course URL or the title you've added to the player?
Also, for the next button have you tried using the enter key vs. the spacebar?
If you're still having issues with JAWS, it would help to know what version you're using, what browsers you're testing it in, and what update of Storyline you're on. Then we can look at testing using the same set up as well. If you want to share a sample .story file, that's also helpful so we can try to recreate your experience.
I have seen the same behavior, using JAWS 2018 in all browsers. Each time a slide starts the course title included in the player is read by JAWS. I think it makes little sense as the title is always the same, it should read it only on the first slide at most.
The main problem is when the slide has a video or audio, the reading of the title overlaps with the audio in the media. And there is little we can do to avoid it, apart from removing the title.
The problem that Carlos explains is definitely an issue for us as well. We need to have the title displayed on the player skin, and delaying the start of the video on the slide does not leave a very good experience for our users who are not using screen readers.
Hi Carlos and Kristin. Currently, the course title will be accessible to the screen reader on every slide.
I understand what you're saying about that element interfering with audio or video that starts up automatically. We make some recommendations about triggering audio or video to satisfy accessibility best practices. Check out page 20 of our e-book, 6 Best Practices for Designing Accessible E-Learning.
Avoid starting videos automatically, since learners with visual impairments need full control over video playback. Or, if you want videos to autostart for nonimpaired learners only, you could keep the option on, but use a variable to suppress it if learners identify themselves as visually impaired.
Hi there, Nicole. Thanks for your update and for opening a case with our team!
We're seeing JAWS read the course title again so we'll need to take a second look at this behavior. I'm really sorry this problem is back, and we'll keep this discussion updated on any new developments!
We are also experiencing this issue as well. The title is being read automatically on every slide - I can only imagine how frustrating this is for JAWS users.
Thanks for chiming in and letting us know you're still having issues. No updates yet, but we'll be sure to jump in here as soon as we have any progress to share.
Hi! Is there a a way to use e.g. Javascript to detect if there is a screen reader and adjust the audio/video to start after a certain time (after reader has read the title)?
I'm having a somewhat similar issues with the NVDA screen reader, where it reads through the entirety of each slide twice. My guess is that the title is somehow set as the entire slide text, but I can't figure out how to fix it. I've attached my project for reference.
Thank you for sharing your project! I was able to test it on my end using NVDA, but I do not hear the slide content repeating. You might be noticing that if you launch a course, NVDA starts reading the slide content until you tab or arrow to a part on the slide. Does this sound similar to what you're experiencing?
If not, please let me know what slide is being repeated, and investigate the particular slide.
Yes, that might be what's happening-- NVDA reading the slide content automatically, and then reading it again when you tab or arrow. Is there a way to stop it from reading the slide content before you tab or arrow to another part of the slide? Or will users expect that sort of behavior?
I've also noticed that it doesn't seem to happen on every slide. It happens more on the ones where the female character is pointing to a poster of text, and less on the ones with two characters talking to each other.
Great question! Users should expect NVDA to begin reading automatically. This is a feature that is beneficial to users who might have a visual disability.
If there is already audio on a slide, the NVDA will not read automatically. This is to prevent audio overlapping.
Let me know if there is anything else we can help with!
26 Replies
Hi Cody,
It's going to read through all the items on the slide, including the project title. You can look at skipping elements of the player as detailed here. Take a look at the steps here to get started!
Is there information on this for Storyline 360? I see this info is for Storyline 2 and only works with Flash. What a about a Flash with HTML5 fallback?
Thanks,
Hey Cody! The method in the article Ashley shared also works in Storyline 360. Flash/HTML Fallback should work--you can check out the supported browsers in our documentation on Storyline 360 Accessibility in Published Courses.
Let us know if you have any other questions!
I am having this issue, as well. JAWS reads the filename at the beginning of every slide. When I press the space bar to skip player navigation, it skips most of the navigation but still goes to the PREV and NEXT buttons, which is good - I want it to do that, but it also reads the filename each time it goes to a new slide. In addition, when it goes to the new slide, the "NEXT" button is highlighted but pressing the space bar does not activate it (it just reads "space") until you use the tab key again to go to the slide items in the tab order and then back to the PREV and NEXT buttons.
Thanks -
Miriam
Hi Miriam,
Is it reading the file name, the course URL or the title you've added to the player?
Also, for the next button have you tried using the enter key vs. the spacebar?
If you're still having issues with JAWS, it would help to know what version you're using, what browsers you're testing it in, and what update of Storyline you're on. Then we can look at testing using the same set up as well. If you want to share a sample .story file, that's also helpful so we can try to recreate your experience.
Hi,
I have seen the same behavior, using JAWS 2018 in all browsers. Each time a slide starts the course title included in the player is read by JAWS. I think it makes little sense as the title is always the same, it should read it only on the first slide at most.
The main problem is when the slide has a video or audio, the reading of the title overlaps with the audio in the media. And there is little we can do to avoid it, apart from removing the title.
The problem that Carlos explains is definitely an issue for us as well. We need to have the title displayed on the player skin, and delaying the start of the video on the slide does not leave a very good experience for our users who are not using screen readers.
Hi Carlos and Kristin. Currently, the course title will be accessible to the screen reader on every slide.
I understand what you're saying about that element interfering with audio or video that starts up automatically. We make some recommendations about triggering audio or video to satisfy accessibility best practices. Check out page 20 of our e-book, 6 Best Practices for Designing Accessible E-Learning.
I am experiencing a similar issue. I am not displaying the course title in the player, however, Jaws keeps repeating the title on every slide.
Hi Nina,
Sorry, you've hit this bug! It's one our team is aware of and tracking so I'll keep you posted here!
Great news, folks! We fixed the issue you reported where JAWS would read the course title even though it was disabled in the Player features.
Here's how you can update Storyline 360 to see all the latest features and fixes. If this problem resurfaces, please record a Peek 360 screencast for me, and I'll be happy to help!
Hi this is still happening for me. The title is not checked but the JAWS reader keeps reading it on every slide
Hi there, Nicole. Thanks for your update and for opening a case with our team!
We're seeing JAWS read the course title again so we'll need to take a second look at this behavior. I'm really sorry this problem is back, and we'll keep this discussion updated on any new developments!
I am also experiencing this issue. Is there any further progress to stop the title being read on every page?
Hi Claire,
Thanks for reaching out and sharing that you are running into a similar issue with your course.
I do not have an update to share at this time. It is still open with our team.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
We are also experiencing this issue as well. The title is being read automatically on every slide - I can only imagine how frustrating this is for JAWS users.
Hi there, Bill.
Really sorry for the trouble, and I can appreciate how frustrating this has been.
While I don't have a timeline for a fix just yet, I'll keep this discussion posted as soon as new information becomes available.
I'm also having this problem with JAWS reading out the full title of the course every time a new slide loads. We're using a custom player.
Hi Rachel,
Thanks for chiming in and letting us know you're still having issues. No updates yet, but we'll be sure to jump in here as soon as we have any progress to share.
Hi! Is there a a way to use e.g. Javascript to detect if there is a screen reader and adjust the audio/video to start after a certain time (after reader has read the title)?
Happy Tuesday, everyone!
Update 40 for Storyline 360 is live: We fixed the issue where JAWS screen readers repeated the course title on each slide.
I'm having a somewhat similar issues with the NVDA screen reader, where it reads through the entirety of each slide twice. My guess is that the title is somehow set as the entire slide text, but I can't figure out how to fix it. I've attached my project for reference.
Hi Sarah!
Thank you for sharing your project! I was able to test it on my end using NVDA, but I do not hear the slide content repeating. You might be noticing that if you launch a course, NVDA starts reading the slide content until you tab or arrow to a part on the slide. Does this sound similar to what you're experiencing?
If not, please let me know what slide is being repeated, and investigate the particular slide.
Yes, that might be what's happening-- NVDA reading the slide content automatically, and then reading it again when you tab or arrow. Is there a way to stop it from reading the slide content before you tab or arrow to another part of the slide? Or will users expect that sort of behavior?
I've also noticed that it doesn't seem to happen on every slide. It happens more on the ones where the female character is pointing to a poster of text, and less on the ones with two characters talking to each other.
Hi Sarah!
Great question! Users should expect NVDA to begin reading automatically. This is a feature that is beneficial to users who might have a visual disability.
If there is already audio on a slide, the NVDA will not read automatically. This is to prevent audio overlapping.
Let me know if there is anything else we can help with!
This discussion is closed. You can start a new discussion or contact Articulate Support.