The problem we're having is that once a user tabs into the articulate object, they can no longer leave that object. Tabbing simply rotates them around in the object. It even locks out standard browsing shortcuts like ctrl-home. Alt/Shift/Ctrl Tab works, but that doesn't help. I'm trying to figure out a way to give control back to the student, or to put some kind of navigation within the object. Exit course doesn't work either. The only thing we've found that works is to grab the navigation links from D2L and add those, but that's not a great solution.
I don't have specific experience with Brightspace (D2L), but I'd want to test the file in another environment to parse out whether this is a file issue or LMS related.
Have you had a chance to test the output in SCORM Cloud? I'd be happy to help you with that testing, if you'd like!
It doesn't seem that we heard back from Adam, but we'd gladly test out your file too! Our team often uses SCORM Cloud as a baseline testing for LMS exports, and we'll also test using the browsers and screen readers listed here in our article on accessibility.
If you're able to share your file you can upload it here using the Add Attachment button at the bottom of the reply window in the discussion here.
Does anyone have a solution for accessibility of Articulate Storyline on D2L? I have the same problem. After spending a lot of time developing interactive Storyline project and imported to D2L, it blocks navigation using keyboard alone and a screen reader. If anyone have an answer, I would appreciate that.
Sorry for the late reply. When I imported the zip Storyline file to D2L and I started navigating with keyboard and a screen reader (NVDA), it works fine. The problem started when I revisit the integrated file after a week and I can't access the Resume and Restart button using keyboard and a screen reader as I did in the past. I refreshed the page and cleared cache. None of them works. Is there any settings I need to do when publishing the file from Storyline?
First, I noticed that your email signature came through when you replied via email. You can remove that if you would like by clicking Edit beneath your response. Here’s a quick Peek video if you need help.
For the navigation piece, what happens when you attempt to use the keyboard to navigate to those two buttons? Are they skipped entirely or does something else occur?
What version of Storyline are you using and what browser are you viewing it in? Also, have you tested it with another screen reader like JAWS?
Thank you for the video. I couldn't navigate through both buttons on the Storyline. It actually skipped to other buttons, part of D2L. I used NVDA as a screen reader. I'm using Storyline 360 with Chrome 72. It worked before but it didn't after the Storyline file had been accessed for a while. Any suggestions?
So it may be the NVDA reader, or as you mentioned D2L may be advancing to those buttons. I'd reach out to the D2L team to see if they had other thoughts and you could also look at testing in SCORM Cloud which is a standard for LMS testing.
9 Replies
Thanks for your post, Adam!
I don't have specific experience with Brightspace (D2L), but I'd want to test the file in another environment to parse out whether this is a file issue or LMS related.
Have you had a chance to test the output in SCORM Cloud? I'd be happy to help you with that testing, if you'd like!
Did you ever get a response or come up with an answer to this? We have had to take all articulate files out of Brightspace due to Accessibility.
Hi Amy,
It doesn't seem that we heard back from Adam, but we'd gladly test out your file too! Our team often uses SCORM Cloud as a baseline testing for LMS exports, and we'll also test using the browsers and screen readers listed here in our article on accessibility.
If you're able to share your file you can upload it here using the Add Attachment button at the bottom of the reply window in the discussion here.
Does anyone have a solution for accessibility of Articulate Storyline on D2L? I have the same problem. After spending a lot of time developing interactive Storyline project and imported to D2L, it blocks navigation using keyboard alone and a screen reader. If anyone have an answer, I would appreciate that.
Hello Supada! It sounds like you're also seeing tabbing stay inside Storyline instead of allowing users to go into the D2L interface.
Is there a difference if you launch the Storyline course in a new window that users can close when they are ready to return to D2L?
Hi Crystal,
Sorry for the late reply. When I imported the zip Storyline file to D2L and
I started navigating with keyboard and a screen reader (NVDA), it works
fine. The problem started when I revisit the integrated file after a week
and I can't access the Resume and Restart button using keyboard and a
screen reader as I did in the past. I refreshed the page and cleared cache.
None of them works. Is there any settings I need to do when publishing the
file from Storyline?
Thank you!
Supada
Hi Supada,
First, I noticed that your email signature came through when you replied via email. You can remove that if you would like by clicking Edit beneath your response. Here’s a quick Peek video if you need help.
For the navigation piece, what happens when you attempt to use the keyboard to navigate to those two buttons? Are they skipped entirely or does something else occur?
What version of Storyline are you using and what browser are you viewing it in? Also, have you tested it with another screen reader like JAWS?
Hi Ashley,
Thank you for the video. I couldn't navigate through both buttons on the Storyline. It actually skipped to other buttons, part of D2L. I used NVDA as a screen reader. I'm using Storyline 360 with Chrome 72. It worked before but it didn't after the Storyline file had been accessed for a while. Any suggestions?
Hi Supada,
With Storyline 360 we support these screen readers with HTML5 and Flash courses:
Firefox users might need to upgrade JAWS.So it may be the NVDA reader, or as you mentioned D2L may be advancing to those buttons. I'd reach out to the D2L team to see if they had other thoughts and you could also look at testing in SCORM Cloud which is a standard for LMS testing.
This discussion is closed. You can start a new discussion or contact Articulate Support.