Simple way to get rid from autoplay button in Adobe Captivate 2019

I understand the frustrations with this issue, but whether the learner has to click this initial play button or another one we place on a later slide is something of a moot point to me because either way the user MUST click something.

This is the point I was making.  Getting past Adobe's button on the first slide is NOT a complete solution.  If you make this coding change to a module with audio, and do not in some other way still force the user to click something before the audio is due to play, then you will be deluged with support calls from users telling you the course is malfunctioning because the audio doesn't come in when they expect and then suddenly does appear later when they do something.  Your management will blame YOU, not the browser.  They pay US as the developer to know enough to avoid such annoyances.

The browser manufacturers have implemented this limitation on multimedia files playing automatically because of the egregious way internet marketers have misused autoplay on websites with adverts.  Due to the volume of complaints from end users, the people behind the browsers decided enough was enough.  Unfortunately, multimedia e-learning courses like the ones we create with Captivate are suffering collateral damage in this war.

Like it or not, the e-learning industry is little more than a flea on the tail of an elephant called the Internet and as such we have absolutely no power to force the browsers to do anything.  We just need to workaround this issue the same way we work around all the others, but without making the issue any worse.

I think Adobe made the correct call in putting this button on the first slide and enforcing the way it works because then non-technical developers (which are the majority of people using Captivate) are unlikely to get into trouble if they just run with it.  Sometimes a little knowledge can be a dangerous thing...

I would add that I will be very interested to see how long this fix continues to work.  Web browser manufacturers are continually closing off security and usability loopholes.  They implemented this change for a good reason.  I would be very surprised to see them so easily defeated by a single line of code.