Auto play audio in Rise?

I am currently in the review stages of a Rise module. 

The module contains storyline blocks that have audio that plays at the start of each timeline. 

Usually, the Storyline section will have a black box and a play button for users to start the content. This is how I would like it. I can control how the user has to view the content before continuing which is great!

However, recently I have been finding that the storyline content audio will start playing by itself even when the user has not reached the part of the Rise Module where the audio is applicable. This usually making users confused and unsure of what part they are meant to be on. 

The option to have audio autoplay once a storyline block is covering the majority of the screen would resolve all these issues. 

I have also found that the Storyline blocks usually work the way I would like in Chrome, however, it is more likely to autoplay in Microsoft Edge. Maybe some clarity surrounding why this occurs would be great so that we can suggest to the users to open the module in chrome if required. 

Any help is greatly appreciated!

I would also like Autoplay to be added to Rise

A few months ago I saw a post that the autoplay was in development.  Any update?  I really need it.

I agree with all comments in this and other threads about the need for auto play audio, it adds to the experience and drives engagement.

Matthew makes a good point, but you could have a disclaimer at the start of your training module about data usage. 

Learning is about engagement and a voice over for content supports learners who perhaps don't read well. 

This is a must have in my book, and everythign else about Articulate is great for me so far, lack of this feature is a real let done.

I know this is an older thread but wanted to let people know that the reasoning behind not auto-playing media is not just because of stricter rules.

For any media to auto-play, means the user/learner is suddenly using data. If they are not on a Wi-Fi network (or for some reasons, have their mobile device set to expend cell/tablet data first), then those are all automatic dings on their data-usage allotment. 

You can see where this might cause issues for the user/learner. If all media auto-plays, and they surpass their data-usage, suddenly they are on the hook for data-overage charges. This in particular is of concern for users/learners who rely solely on their mobile device for internet accessibility, and accessibility towards whatever eLearning content you are creating, which can thus become a concern for the employer.

Ways around it of course, but this is why some developer programs (and some rules/regulation around this exact topic) have been deliberately designed this way (and I believe I recall RISE even stating that was their intent when this first rolled out). I'm not sure of the percentage, but a lot of html 5 stuff is shifting towards that design format as well. Just food for thought.

+1 for autoplay (and just a notice: not all of your customers make note here, most of them (us :-| ) simple started to look for other tool)

I have created the storyline block and have imported that block into RISE, but how do I enable the Autoplay feature with the storyline block that's imported to RISE? The learner still has to press "Play" to initiate the storyline block. This is what I would like to avoid and instead, when the learner scrolls to this storyline block, imported into RISE, I would like for it to play for them.

I would also like to add my vote in for putting Autoplay Audio on the feature roadmap for Rise 360!

I would like to also vote for the autoplay here. For those who are computer illiterate this is a key part to teach navigation. I literally would have people looking at the play button asking "what do I do?"

Adding my vote for auto play as well.  Glad to see it is now on the roadmap and hopefully it will be added soon.  

Unfortunately, the lack of this capability detracts from all of the elegant solutions that we could do with Rise.  It is essential for our applications and we cannot use RIse 360 with the expectation of the user to click repeatedly for the audio.