Forum Discussion
Closed Captions in Exported Video File
Hi there,
I am trying to test if I import an MP4 video file and add closed captioning in the Storyline 360, when I publish it as a video my closed captions are not displaying. I can see them in t...
Hi, everyone!
I have some great news to share. We just released another update for Storyline 360. In Update 73, we’ve included important fixes and new features!
One new feature we’ve included:
Boost video accessibility by including closed captions when publishing projects as MP4 video files.
To take advantage of this update, launch the Articulate 360 desktop app on your computer, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
Hey, Kim and welcome to the E-Learning Heroes community! We're glad you're here. 😀
It sounds like you've run into some trouble with closed captions you added on a slide where there was a video? Did you add the captions using the Storyline option outlined here or in an external video editing software? If you've added them from inside Storyline, you'll only see them in Preview/publish by toggling the Closed Captions button on the player. The closed captioning button on the course player is enabled by default.
Some other tips for interacting with the closed captioning button:
- The closed captioning button may not always be visible throughout your course. It’s only visible when captions are available on the current slide or layer. It’ll disappear for slides and layers that don’t have captions. This gives learners a visual clue when captions are available.
- When a learner clicks the closed captioning button to turn on captions, the button will remain turned on throughout the course until the learner clicks it again to turn it off.
Let me know if that sheds any light on your setup, or if you still need more help we can take a look at your .story file. You can upload at this link using the Add Attachment button or you always have an option to share privately with our Support Engineers. Either way, we'll delete it when done testing.
