Closed Captioning turning off after layer showing
Jun 18, 2019
By
Graham Cohen
Hey everybody. Has anyone else experienced this. I have a course built with ADA compatible closed captioning as an option. I have many slides with layers that activate via a button for best practices which stop playback of the base layer. Think of it as a window that pops up giving the student a best practice. They then click on an "X" to close the layer and continue on. Here's the problem. When you click on the button to launch the layer the closed captioning button on the player disappears and turns off the CC with no way to turn it back on. This obviously now puts my course out of compliance for ADA. See my attached images as an example. Any help would be much appreciated. I think this is a bug.
14 Replies
By the way i'm using SL3.
Ok. I does appear to be a bug. I can prevent this if I DON'T stop the base layer from playing when the student clicks on the button to show the layer. If I turn that feature off everything stays in place. However, my layer covers half of my screen and the student is missing the learning that is going on. I need to stop the playback when they click this button which turns off my CC. This is a huge problem for ADA compliance.
Hi, I tested this just now and it works as you would expect. The best practice pop up - is that a hidden image that appears when you click the light bulb, or on a layer? If it's on a layer, did you hide the base objects on the layer? If you hide base objects on a layer the CC button will disappear.
Hi Noel. It's on a layer. I have show base layer objects enabled as it's a pop up. I can replicate it every time now. I've been playing with this for over 2 hours and it's baffling. Here's how my slide is set up.
Pop up layer is a single layer with a simple box with text and a shape button in the corner that acts as a button to close the layer.
My base layer has 1 image, 1 text box and 1 shape. I also have an audio file with closed captioning attached to it. (must have CC attached)
I think you're right and it's a bug. I have replicated what you describe and it works fine for me.
The only other thing I would check before contacting support is to create a new file and put one audio file in and some CC attached and set it up the same way to see if you have the same issue. If you do, then a bug, if not, then maybe the file is glitchy. Sometimes uninstalling and reinstalling Storyline can sort out bugs and ensuring you're on the latest version.
Heres a quick replay I did to show what i'm seeing. I just made a small project with new items to test and I can make it happen on that too. I have submitted a case to support as I can replicate it. I'll be sure to post on this once I get it solved.
Out of curiosity Noel, are you on SL3 or 360?
Out of Curiosity Noel. Are you on 360 or SL3?
here's a replay of the test file I just created. You'll see I can duplicate it even in a new file.
I have both loaded but tested it in SL3 - so I guess it's good to know that it can work fine in SL3.
Your video showed what I would get if I hid the base objects on the layer - but if you're just adding a text box with a close button then you should not have the issue you have.
Interesting. So you can get it to work just fine then yes? Wonder if it has something to do with my computer setup? I've uploaded my two files to support and they are working on it right now. As soon as they respond i'll update here. The key is you must pause the base layer in order for the button to turn off. I'm going to try adding a hidden box and have my button make the box visible when pressed and not use a layer. I'll add a trigger to pause the base layer and another to restart it when the box is re hidden and see if that works for me. Thanks for the help Noel. appreciate it.
Boom. That worked. I changed my setup to have a hidden pop-up box on my base layer instead of a regular layer. I added a trigger to pause the timeline when my button was pressed and another trigger to restart it when my close button is pressed. the CC button stayed on and is working fine. At least i have a work around now.
Hi Graham,
Thanks for popping back in to share your workaround.
I appreciate you mentioning that you were working with our support team as well. That allowed me to take a look and see that Renz is assisting you and it looks like we're doing some further investigation on this issue as well.
I've linked this conversation to the report as well so that we can share any updates here.
No problem. Noel was a big help.
This discussion is closed. You can start a new discussion or contact Articulate Support.