Forum Discussion
Any Updates on Considering Auto Play Media in Rise?
It is my understanding that the main driver for web-browsers having stricter auto-play policies is to prevent intrusive content from interrupting the user experience, not to prevent included audio within a chosen interaction.
That being said, I think Rise needs auto-play for its audio to stay ahead of the curve as a leading provider. I have full confidence that the development team can come up with a workable solution that still delights both designers and end-users and remain well within the web-browser policies and functionality.
Most web-browsers require some user interaction with the content to indicate to the asset that it is OK to play. It could be as simple as letting a section's trigger also act as the interaction that meets the auto-play policy criteria.
Please don't give up on this improvement.
Right on, Jeff! I was very disappointed when reading Alyssa's response. I'm on the verge of buying Adobe Captivate again.
Best wishes,
Kate Goebel
- JeffMomsen-4cf06 years agoCommunity Member
It's so funny, I have been monitoring this thread VERY closely as improving the narration experience is so necessary, along with the RISE path towards accessibility (specifically the screen reader compatibility).
I was delighted to see the flood of supporting comments from the community to champion this fix but even more happy to see a colleague that I know and respect chime in!
- GregNickerson6 years agoCommunity Member
Nice to hear from you, Jeff!
I've made official feature / enhancement requests for auto-play SEVERAL times in the last two years. I'm losing hope they will address this need. I encourage everyone to add your thoughts to the feature request list as well!
Here is the link:
https://articulate.com/support/contact/feature-request
I posted the following six months ago:
"Please add the auto-playback feature! When taking an e-learning module on a small device, it is even more important that we are able to auto-play audio/video! The "screen space" is already limited, and making a user "swipe/scroll around" for a play button is unfair.
If we are truly keeping the learner in mind, the path to least resistance should be at the forefront of development. "
All the best to you and yours, Jeff!
-Kate
Related Content
- 7 months ago
- 8 months ago