Forum Discussion
Accessibility Issue: No Audio Options for Feedback in Rise 360 Knowledge Check Questions
I’m running into an accessibility issue in Rise 360 and wanted to see if anyone else has come across this or found a good workaround.
Right now, Rise lets you add audio to the question prompt in Knowledge Check blocks, but the feedback (Correct / Incorrect / Continue) is text‑only. There’s no option to upload audio or embed anything for learners who need feedback in an audio format.
This becomes a problem for learners who benefit from multimodal feedback — for example, people with dyslexia, higher cognitive load, or anyone who relies on audio reinforcement to process information. For accessibility‑focused courses, text‑only feedback doesn’t always meet their needs.
I know you can use Storyline blocks as a workaround, but they don’t always fit smoothly into a Rise‑based course. Branching pages can work too, but they add extra steps for something that should be simple.
Feature request: It would be really helpful if Rise allowed audio (or even basic media blocks) inside feedback fields so we can offer feedback in multiple formats. Even a simple “upload audio” option would make a big difference.
Has anyone found another way to handle this directly in Rise, or is everyone relying on Storyline blocks? And could this be something added to the Rise roadmap?
Thanks — interested to hear what others have found.
1 Reply
Real gap — I've run into this one too. No way to do it directly today: audio in a Knowledge Check block only attaches to the question prompt, not the feedback fields.
Two workarounds that actually work:
1. Audio block under the Knowledge Check. Add a Rise Audio block right beneath it with verbal feedback for each choice ("If you chose A, here's why that's right..."). It's not conditional on the answer, but learners still get the audio feedback loop.
2. Storyline block. Build the question as a Storyline question slide — feedback layers there take full audio. More setup, but it's the real fix when the audio matters.
One framing tip for the feature request: screen reader users already get the feedback read aloud, so the gap is sighted learners who benefit from hearing it too. That framing helps product prioritize it. Log it on the Ideas board (Exchange > Ideas) if you haven't — that's where these get tracked.
