What's impacting autoplay in Chrome?

Chrome recently updated its autoplay policies and these changes impact video playback with sound.

For instance, you may no longer be able to hear audio when a training video or SCORM file automatically launches. You will need to pause and resume the training to prompt audio to return.

As an admin creating new lessons, a best practice to work around Chrome's new behavior is to avoid adding a video as the first card in your lesson. Placing the video card further into the lesson will require users to engage with the training and this activity will tell Chrome to allow audio to continue. 

You can also loop in your IT team to review the Chrome's policies and settings to help set these new autoplay related enterprise policies:

• The "AutoplayAllowed" policy controls whether autoplay is allowed or not.
• The "AutoplayWhitelist" policy allows you to specify a whitelist of URL patterns where autoplay will always be enabled.

Why were these changes made?

Chrome, along with other major browsers, have adopted stricter autoplay policies in an effort to improve user experience by giving them more control over video playback.

Chrome's autoplay policies are:

• Muted autoplay is always allowed.
• Autoplay with sound is allowed if:
  • User has interacted with the domain (click, tap, etc.).
  • On desktop, the user has previously played video with sound.
  • On mobile, the user has added the site to their home screen.
• Top frames can delegate autoplay permission to their iframes to allow autoplay with sound.