If your Articulate Rise audio isn’t playing, do not immediately replace the audio file. In Rise, the issue is usually tied to the lesson block, browser settings, published output, or the learner’s device. Use this sequence to isolate the cause quickly.
Confirm The Audio Block Is Configured
Open the Rise lesson in Edit mode and locate the affected Audio block. Select Edit and confirm that the file appears in the block and shows a duration. If the audio was recently replaced, preview the lesson before making additional changes.
Check the block’s playback behavior. If the audio is set to play automatically, some browsers may prevent it until the learner interacts with the page. Change the setting to let learners select Play, then preview again. This is the fastest way to identify an autoplay restriction.
Test In Preview And A Supported Browser
Select Preview in Rise and test the same lesson in a current version of Chrome or Edge. Turn up both the computer volume and the browser tab’s volume. A muted tab is easy to miss, particularly when reviewing several courses at once.
If audio works in Preview but not in the published course, the audio file itself is not the problem. Continue with the publish and hosting checks.
Republish The Course Correctly
Publish a fresh version of the course and upload the complete published package to your learning management system or web server. Do not upload only a portion of the files or rename files inside the package. Rise relies on the published folder structure to locate course assets.
If your LMS supports SCORM, publish for the exact SCORM version required by that LMS. Then launch the course from the LMS rather than opening an individual HTML file from your computer. Local testing can create behavior that learners will never see, and the reverse can also be true.
Rule Out Learner-Side Restrictions
Ask the learner to test in an incognito or private browser window. This removes many extension, cache, and cookie issues from the equation. They should also disable ad blockers or privacy extensions temporarily, confirm their device is not muted, and test with headphones if corporate audio hardware is involved.
If only one learner cannot hear audio while others can, focus on their browser, device, and network policies. If no one can hear it after publishing, return to the audio block and republish a clean package.
Looking for Rise training? Check out our live, instructor-led 2-hour Rise class.