Forum Discussion
IMPORTANT! - a fix if you have a PLAY button appearing at start of courses
OK, Articulate rolled out an update to Storyline and it seems that now when publishing a course, instead of auto-playing (as before) it now puts a nasty big PLAY button on the first screen.
Hopefully Articulate will roll out a fix (very!) soon.
In the meantime, I have discovered that AUDIO on the opening slide will cause this. Removing the audio, removed the PLAY button and things went back to normal.
Therefore to get round the issue, try what I did - create a tiny opening slide of a flat colour (same as your project background) and set it to be your opening slide.
Worked well for me, and thankfully I can now stop hearing screaming from my clients.
113 Replies
Is a quick fix to have 2 slides. The 1st slide look the same as the second but only last 0.1secs, then the second slide can come in with the audio?
Hi David,
This is a method a few other users have used but the first slide needs to have some type of user interaction to allow the autoplay to occur after that. The user interaction is what is telling browsers like Chrome that the user would like the media elements to play automatically.
I understand why this was added, but that play button looks pretty bad. The triangle could at least be centered on the button.
Hey everyone,
This article may offer a workaround for those that can adjust the settings of their Chrome browser. You can disable the autoplay-policy flag by changing it to "no user gesture required"—that should allow the course to autoplay as before.
https://9to5google.com/2018/02/15/how-to-disable-autoplay-videos-chrome/
Hope that helps!
I'm having this issue as well. Because I have a menu, I don't want to add a blank slide w/o audio to open - because it will show up in the menu OR I must manually go into every file and remove this from the menu.
Any idea when this will be dealt with?
Matthew may have the best idea here:
https://community.articulate.com/discussions/articulate-storyline/chrome-66-autoplay-policy-changes
Same issue. Post upgrade, users in Firefox 52.7.3 are prompted with a Play button when launching a course. This appears on a basic Welcome slide which includes a triggers to auto-advance the slide when the timeline ends or advance forward when the user clicks next.
Yes, that fix worked for me. The slide numbers are off because of the additional slide, and it looked silly in the menu after deleting the extra screen there to be starting at 1.2. (Of course not a problem unless you need to number the screens in the menu.)
I worked around this by leaving the audio-less, 1/4 second screen at 1.1, then moved the real first screen to the end of the scene, and adjusting the navigation accordingly. Being there, it could be hidden in the menu without affecting the screen numbering.
It's worth noting that the play button is not showing keyboard focus, is not detected by JAWS and does not appear responsive to any keyboard commands I've tried, so it essentially renders projects inaccessible.
Hi Douglas,
Thanks for bringing this up here! It's something I also reported to our team, and we're looking into this right now. While we look into this, one option is to create your own first slide with a play button that is accessible, as Chrome is looking for the user interaction to indicate that they would want media to autoplay.
I'll keep you posted here as soon as I have any other info to share.
Hi Everyone,
Just looking for some clarification... Is everyone upset with the Articulate fix because the play icon is not attractive to have at the beginning of the tutorial or is there another underlying reason? I admit that I would rather not have the play button, but it does fix the issue for us in our LMS.
Thanks!
Hi Jamie,
I also imagine it's frustrating to have a course that could "stop working" through no fault of your own. Luckily, enough folks have been vocal about this change with Google, and they've temporarily rolled back a part of the update. We have a bit more info about that here, and our plans to continue working on the content updaters, and updates for earlier versions of Storyline 2 and Studio '13 so that you're ready when they reinstate this policy.
the workaround works for us here..I just created a company logo slide with a "start" button so that took care of the other Chrome issue of not playing audio (on the second slide) the first time around) cause the user is forced to click on something...
Hey everybody. I'm excited to let you know that we just released update 17 for Storyline 360! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where in HTML5, the course does not automatically play in Firefox when audio or video is added to the first slide.
Even more importantly, we made the play button that appears at the beginning of courses accessible. You can tab to the play button, and press the space bar or enter key to activate it.
Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!
Hi, the play button issue has only just started happening to me with the latest update in 360. Super confused.
