How to Autoplay Audio in Articulate Rise

Sometimes the audio in your Rise course is a critical part of the experience—not an optional extra. In those cases, an autoplay option can make a big difference. Because if learners have to find and click the play button manually, there’s a chance they might miss it.

Articulate Rise Tips and Tricks: How to Autoplay Audio in a Rise Course

Mighty adds a simple autoplay toggle to the native Articulate Rise audio block, so your audio can start when the learner reaches it. That opens up a few useful patterns: setting the tone at the beginning of a course, reading on-screen text aloud, or adding context without asking learners to take one more action.

The native Rise challenge#

In the default Articulate Rise 360 audio block, learners need to manually select the play button.

That’s often the right choice. Autoplay can be distracting if it’s overused, and learners should usually stay in control of media playback.

But there are cases where click-to-play gets in the way of the instructional intent. In the video, John walks through two common examples:

• Using an audio track at the start of a lesson to set the tone for the course.
• Using audio to read or supports text on the screen, which can be especially helpful for English as a second language scenarios or when you want to provide additional context.

In both cases, the issue is the same: if the learner doesn’t click the audio file, they may miss something you intentionally designed into the course.

What Mighty adds#

With Mighty, you can select an audio block in Rise and use the Mighty controls to turn on Autoplay.

Don’t worry—you’re not just forcing audio to play the moment the course loads. You can place the audio where it makes sense instructionally, then let it begin when the learner reaches that point in the lesson.

How to enable autoplay on a Rise audio block#

Here’s the workflow shown in the walkthrough.

1. Open your Rise 360 course.
2. Go to the lesson that contains your audio block.
3. Add or locate the native Rise Audio block you want to autoplay.
4. Select the audio block in the Rise editor.
5. Open the Mighty modification controls for that block.
6. Turn on Autoplay.
7. Return to the main course view.
8. Select Preview to test the lesson as a learner.
9. Scroll to the audio block, or begin the course if the audio appears at the top of the lesson.
10. Confirm the audio starts automatically when the block comes into view.

That’s it. No custom code, no rebuilding the interaction, and no extra learner instructions like “Click play before continuing.”

Example 1: Set the tone at the start of a course#

In the first example from the video, the course is about building influence inside an organization. Before learners move into the main content, the designer wants to create a calm, focused tone with a Zen-style audio file.

Without autoplay, the opening experience depends on the learner clicking the audio block. You could add instructions, of course, but that adds friction right at the moment you want the experience to feel seamless.

With Mighty’s Autoplay option turned on, the audio starts as soon as the learner begins the course. The audio becomes part of the designed opening rather than a separate media object the learner may or may not use.

This is a good fit when the audio is meant to support the mood or pacing of the lesson, such as:

• A short ambient track at the beginning of a reflective module.
• A brief welcome message that orients learners before they scroll.
• A scenario setup that should be heard before learners see the first decision point.

If the audio is just decorative, think carefully about whether it needs to autoplay. But if it genuinely supports the learning moment, autoplay can make the experience feel much more intentional.

Example 2: Support text with spoken audio#

The second example in the walkthrough is an Infection Prevention course. In this lesson, the audio is used to read or support text on the screen.

John calls out a few possible uses here: maybe it’s an English as a second language support strategy, maybe it’s text-to-speech-style reinforcement, or maybe it’s additional information you want to present alongside the visible content.

The behavior is especially useful because the audio doesn’t need to play immediately when the lesson loads. In the preview, the learner lands on the main page, scrolls down, and when the audio block comes into view, it starts playing.

The narration begins where the supporting content appears, instead of asking the learner to stop, find the audio control, and press play.

Why this matters for course design#

Rise is great because it creates a clean, scroll-based learning experience. Learners move through lessons naturally, and the best Rise courses tend to reduce unnecessary instructions.

Manual audio playback can interrupt that flow. If you need to write, “Select the play button to hear this section,” you’ve added another instruction the learner has to parse before getting to the content.

Autoplay can help when audio is part of the core learning path:

• Tone-setting: Start a lesson with atmosphere or a short spoken setup.
• Language support: Pair written content with spoken audio for learners who benefit from hearing the text.
• Context: Add narration that explains what the learner is seeing without requiring an extra click.
• Consistency: Make sure an important audio cue is actually heard, instead of hoping learners notice it.

This is also useful when stakeholders expect a more guided experience, but you still want to keep the Rise lesson lightweight and scroll-based.

A quick accessibility note#

Autoplay audio should be used thoughtfully.

Some learners may be in shared workspaces, using assistive technology, or relying on their own pace to process content. If the audio communicates important information, make sure the same information is available in text as well. If it supports on-screen text, keep the written version visible and clear.

Also consider placement. Autoplay audio at the top of a lesson feels different from autoplay audio several blocks down. Test the experience in preview and ask: will this surprise the learner, or will it feel like a natural part of the section?

A good rule of thumb: use autoplay when it removes friction from a purposeful learning moment—not just because the feature is available.

Test it the way a learner will experience it#

After you turn on Autoplay, don’t stop at the editor. Use Preview and move through the course like a learner.

Check three things:

1. Timing: Does the audio start at the right moment, either when the lesson begins or when the block scrolls into view?
2. Context: Is it obvious why the learner is hearing the audio at that point?
3. Content backup: If the learner can’t or doesn’t listen, is the important information still available another way?

This only takes a minute, but it helps you catch the difference between “technically works” and “feels right in the lesson.”

Try it in your next Rise course#

If you’re using audio to shape the opening of a course, support multilingual learners, or provide narration alongside a specific section, Mighty’s Autoplay toggle gives you a cleaner option than asking learners to click play.