The Complete Guide to Rise 360 Accessibility
Everything instructional designers need to know to make Rise 360 courses accessible, written for Rise specifically, not adapted from Storyline.
Rise 360 Accessibility Quick Checklist
A fast, practical pass through your Rise course before you publish it, 19 checks, about 15 minutes.
WCAG for Rise
Rise handles more accessibility structure automatically than Storyline, no toggle to find, but that doesn't make a Rise course automatically accessible. Alt text, captions, and a few interaction types still need your own work.
Rise Continue Block Best Practices
Rise can require a learner to view or complete a block before the lesson lets them continue. This is a real, useful pacing tool, and it also has a real accessibility failure mode: a learner who can't interact with a block the way Rise expects gets stuck with no way to proceed.
What Screen Readers Announce in Rise
Rise's native blocks generally announce well by default, that's one of the real advantages of building in a block-based tool. The gap almost always shows up in the same place: an Embed block carrying custom HTML that Rise has no control over.