Since embedded videos are hosted on a third-party site, there isn't a way for Storyline 360 to detect if one of their videos has finished playing. The closest workaround would be to match the length of the timeline with the duration of the video and restrict the seekbar so that your learners will be required to view the video in its entirety. You can then addd triggers to make the next button available at the end of the timeline.
Of course, the best solution would be to download a copy of the embedded video if you are able and to add the video from a file. This will give you full control over how the video interacts with the rest of the slide.
It is possible with videos hosted on Vimeo or YouTube, or similar platforms that share access to their API. You would have to create an index.html that will hold the embedded link and a few lines of JavaScript that sets up connection to API, and a function that would change the SL variable value when the video ends. This index.html is then imported in to Storyline as a web object. Basically, the state of the next button is set to Normal when Variable changes, and the variable is changed when the video ends (a function inside index.html). Downsides: the index.html folder needs to be renamed every time if there is a change and imported again through the web object edit option. Testing this feature all together requires publishing to Review or LMS. If you are interested in this solution I will upload an example and assist you in setting this up.
I found this helpful article from the Bureau of Internet Accessibility which discusses if embedded videos are accessible. Its a good read and it basically says that embedded videos are generally accessible when using screen readers.
You can also check out this article for more tips on how to make your Storyline 360 courses more accessible:
5 Replies
Hello Anne,
Happy to help!
Since embedded videos are hosted on a third-party site, there isn't a way for Storyline 360 to detect if one of their videos has finished playing. The closest workaround would be to match the length of the timeline with the duration of the video and restrict the seekbar so that your learners will be required to view the video in its entirety. You can then addd triggers to make the next button available at the end of the timeline.
Of course, the best solution would be to download a copy of the embedded video if you are able and to add the video from a file. This will give you full control over how the video interacts with the rest of the slide.
Let me know if you have any questions!
It is possible with videos hosted on Vimeo or YouTube, or similar platforms that share access to their API. You would have to create an index.html that will hold the embedded link and a few lines of JavaScript that sets up connection to API, and a function that would change the SL variable value when the video ends. This index.html is then imported in to Storyline as a web object. Basically, the state of the next button is set to Normal when Variable changes, and the variable is changed when the video ends (a function inside index.html). Downsides: the index.html folder needs to be renamed every time if there is a change and imported again through the web object edit option. Testing this feature all together requires publishing to Review or LMS. If you are interested in this solution I will upload an example and assist you in setting this up.
Thanks. I suspected that but the work around is worth playing around with!
Wondering with the above if accessiblilty is problematic with the solutions above (screen readers etc.) Thanks!
Hi Anne,
I found this helpful article from the Bureau of Internet Accessibility which discusses if embedded videos are accessible. Its a good read and it basically says that embedded videos are generally accessible when using screen readers.
You can also check out this article for more tips on how to make your Storyline 360 courses more accessible: