What you'll learn
- See exactly how Rise's accessibility defaults differ from Storyline's
- Learn what Rise handles automatically versus what still needs a manual check
- Cover all 11 topics, from course structure to assessments
- Know Rise has no auto-advance timing to worry about, unlike Storyline
What's inside
Instructional designers building courses in Articulate Rise 360
- 01How Rise differs from Storyline
- 02Structure
- 03Language
- 04Audio
- 05Video
- 06Images
- 07Color and Contrast
- 08Motion
- 09Keyboard Navigation
- 10Focus
- 11Reading Order
- 12Assessments
Frequently asked questions
Is Rise 360 more accessible than Storyline by default?
In some ways, yes. Rise has no accessibility on/off toggle, its output is not optional, and native blocks are generally keyboard-reachable by default. But that does not mean a Rise course is automatically accessible, alt text, captions, and contrast still need real attention.
Does Rise have the same auto-advance risk as Storyline?
No. Rise navigation is learner-paced by design, there is no auto-advance mechanism to worry about, unlike Storyline's Timing settings.
Can I change tab order in Rise the way I can in Storyline?
No. Rise has no manual override, blocks tab in the order they are laid out on the page. If something tabs in a confusing order, the fix is to rearrange the blocks themselves.
Are Rise's Knowledge Check blocks accessible by default?
Reachability and selection are generally handled for you. Whether the feedback is actually announced to a screen reader is still a manual check today, A11yCheck does not automate that part yet.
How is this different from the Storyline Guide?
This was written for Rise from the ground up, not adapted from the Storyline Guide. It covers the same 11 core topics but every recommendation matches Rise's actual settings, defaults, and block behavior.
Do Sorting and Categorize blocks work with a keyboard?
Not automatically in every case. This is one of the checks A11yCheck cannot verify today, it needs a manual keyboard test.
Related Guides
Rise 360 Accessibility Quick Checklist→
A fast, practical pass through your Rise course before you publish it, 19 checks, about 15 minutes.
The Complete Guide to Storyline Accessibility→
Everything instructional designers need to know to make Storyline 360 courses accessible, with a good and bad example for every check.
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.
Alt Text Guide→
Alt text is a short written description of an image that a screen reader reads aloud in its place. Write what the image communicates, not what it looks like, and keep it under about a sentence.
Storyline vs. Rise: Which Is More Accessible by Default→
Rise is more accessible out of the box because its native blocks handle structure and keyboard access automatically, but it has real gaps of its own: drag-and-drop interactions aren't accessible, and button and tab text always renders in all caps with no way for a course author to change it. Storyline gives full control, which means nothing is accessible by accident, every setting and every tab order has to be deliberately configured.
A11yCheck vs. Built-In and Generic Accessibility Checkers→
Storyline's built-in Accessibility Checker (added May 2025) and generic web tools like WAVE and axe each catch real issues, but neither reviews Rise, neither combines accessibility with course quality and engagement, and neither understands eLearning-specific structure. Here's exactly what each tool does well, and where A11yCheck fits.
Ready to scan your Rise course?
Free during beta. No credit card, no signup required to try it.
Run a free scan →