Forum Discussion
PREVIOUS BUTTON - RECODED
Has anyone created JavaScript or some other fix to coding the previous button to go the last page in sequence vs the last page visited? This is a huge accessibility issue, and hard coding these pages is a nightmare.
Thank you in advance!
7 Replies
Unless something has changed, you can use the trigger to "hard code" where you want a button to navigate. Instead of allowing the trigger to jump to previous, replace previous with the slide you want it to which you want the user taken. No need for JavaScript.
Yes, thank you, Amy. We do that now, but it becomes quite burdensome in time and effort when you have more than 100 pages of content, which is normal for us. It also adds probability of error due to moving targets; pages are often moved around, even after "final" editions. I want to work smart, not hard, so waiting for Articulate to catch on! Or perhaps, someone has found a way to repurpose a system variable?
You might explore this option. You could manage your slide IDs in a JS variable array or object and then reference the IDs dynamically to target the jumpToSlide function. Once you work out the storage and retrieval mechanism, the jump to functionality would be automatic.
Jump To Slide via JavaScript Now Available | Articulate - Community
As someone coming from the adobe world... this is a problem that I just do not understand. WHY would I want the previous button to go to the previous page I was on... not the previous page in sequence.
I would much rather it default to going to the previous in sequence and have a different option when I want it to go to the previous page they were on.It's because "out of the box" functionality is to operate like a web browser, where back takes you back to what you last viewed. If you want to lock the navigation sequence, you can just change the trigger to jump to a specific slide.
Thank you, Amy and Kyle, for taking the time to respond. This is not the first time I've posted about this, maybe the third? Things change and people come up with some pretty creative ways to work around issues. 😁 I understand fully how the button was designed. I was "raised" on the previous/last page visited as well! However, many of us now live in the world where accessibility is a, if not the, top priority, and we must code buttons to go to the previous page in sequence. It is not difficult to do, but the task becomes tedious and time-consuming when you have over 100 pages. The probability for error goes up, which just adds time to development. I was hoping for a simple way to do it via a master slide. No matter, onward!
100% agree. I might even go a little further to say that that having a back button go forward is counter intuitive. Like if I go to google.com>search>click wikipedia>then click another link to resource.com. If I click back I would assume it takes me back to wikipedia, then clicking back again would take me back to google... not to the the resource.com page.
