Weigh in: Is restricted navigation really restricted?
Mar 19, 2014
Most of my clients ask for restricted navigation. Storyline supports restricted navigation which will prevent skipping ahead in the menu. Unfortunately, restricted navigation doesn't do anything to restrict the player controls in the course skin.
Clients complain that the NEXT button shouldn't allow a learner to proceed until timeline end. Learners can skip through a course with restricted navigation by clicking NEXT. Fortunately, NEXT can be restricted by adding a trigger condition to disable NEXT until timeline end. This workaround is cumbersome, but it is available.
More problematic is the seek bar which is bundled with the PLAY/PAUSE button. Storyline provides an option to include both PLAY/PAUSE and SEEKBAR or neither on the course skin. I'll hazard a blunt statement that most courses are published with PLAY/PAUSE so learners can handle workplace interruptions.
The seek bar is unavoidable... unfortunately... that's because the seek bar allows learners to skip content in restricted mode as easily as if the NEXT button were clicked. Should it? Wouldn't it be more in line with restricted navigation if the seek bar allowed learners to skip back, but not over content?