How do I disable unvisited menu buttons in restricted navigation?
Sep 25, 2014
Hi,
I cannot figure this out. This appears to be a major usability oversight in the software design.
Issue:
I would like force users to progress in linear fashion through the course and complete each slide before going to the next. Setting the global navigation mode does this successfully. However the menu buttons on the left that are not active (i.e. the ones ahead of where the user is in the course) still display the hover state and the hand icon giving the appearance that these buttons are active when they really are not.
Question:
I would like to disable the hover state and hand icon on the menu buttons that aren't clickable. Can this be done and if so how? (Note, we do not have Storyline).
This is completely unacceptable the way is now as the menu items feel broken and we would have to add some instruction at the beginning of the tutorial regarding this caveat. This training is expected be used by 5,000 employees so small UX issue would be heavily multiplied in our case.
Please advise.
Thanks,
Mike
2 Replies
Hi Mike and welcome to E-Learning Heroes!
There is not a way to disable this functionality short of not allowing the menu to display to your learners or, as you mentioned, letting them know that they have to proceed with the next button through the course, but can review previously visited slides via menu if needed.
If you would like to share your thoughts with our development team, we have a feature request form here.
Ok. Thank you for your input and quick reply.
This is a shame. Unless I'm overlooking something, Articulate Presenter appears to have no real acceptable restricted navigation option at all. I'd be happy if someone can talk me down or suggest a way that works.
My goal is forced linear navigation with (1) acceptable usability standards and (2) way for users to skip around when reviewing slides already visited.
Option 1: Use Restricted Nav. as designed by articulate.
Problem: Buttons appear clickable which aren't (misleading affordances). Described in original thread above.
Option 2: Use Locked Nav. with custom Previous / Next buttons placed directly on the slides.
Problem: No way for users to skip around to slides already viewed during their review.
The sad thing is the fix for this is probably only a few lines of codes since the "disabled" buttons, in restricted mode, are already coded. Why not just remove all visual hover responses at the same point in the code where the nav function is disabled too. Seems like very low hanging fruit for the development team there.
Mike
This discussion is closed. You can start a new discussion or contact Articulate Support.