Why this matters
Many learners with motor disabilities or repetitive strain injuries use only a keyboard to navigate. Some use switch access or eye-tracking devices that behave like a keyboard. WCAG 2.1.1 says every piece of functionality must be reachable and usable with a keyboard alone — no exceptions for things that feel easier with a mouse.
Storyline 360 example
A Storyline course has a drag-and-drop activity where learners match terms to definitions. There is no keyboard alternative. A learner who cannot use a mouse cannot complete the activity.
Rise 360 example
A Rise lesson includes a sorting interaction. Clicking works fine — but pressing Tab and Enter does not move or place any items.
How to fix it
- 1Test your entire course using only a keyboard — Tab to move forward, Enter or Space to activate, Arrow keys to navigate within components
- 2Every interactive element must be reachable by Tab
- 3Drag-and-drop activities need a keyboard-accessible alternative
- 4Modal dialogs should trap focus so the user does not accidentally leave them
- 5Check that the Tab sequence matches how the content reads visually
Fix in Storyline 360
- 1Open the Tab Order panel from the Home tab
- 2Make sure every interactive element is included in the tab order
- 3For drag-and-drop activities, build a separate dropdown or multiple-choice version that works with a keyboard
- 4Test by pressing Tab through every slide after you publish
Fix in Rise 360
- 1Rise handles most keyboard navigation automatically — focus your testing on custom interactions
- 2Avoid embedding third-party content that blocks keyboard access
- 3Test moving between lessons and completing interactions using only Tab and Enter
Common questions
How do I test keyboard navigation in Storyline 360?
Publish your course and open it in a browser. Put your mouse aside. Use Tab to move forward, Shift+Tab to go back, Enter or Space to activate buttons, and Arrow keys to navigate inside components. If anything is unreachable or unresponsive — that is a failure.
Can learners with motor disabilities use Articulate courses?
Yes, if the courses follow WCAG 2.1.1. That means every feature must work via keyboard, timing must be adjustable, and drag interactions must have keyboard alternatives.
What is tab order in Storyline?
Tab order is the sequence keyboard focus moves through elements on a slide when someone presses Tab. It should follow the visual reading order — left to right, top to bottom — and include only interactive or meaningful elements.
Are drag-and-drop interactions accessible?
Standard drag-and-drop is not keyboard accessible. You need to offer an alternative — a dropdown, a multiple-choice version, or a keyboard-operable drag mechanism. Both versions should lead to the same learning outcome.
Check your course for this issue automatically
Paste your Storyline 360 or Rise 360 Review link and A11yCheck scans for this and 80+ other issues in under two minutes.
Start scanning — it's free