Back-button trigger

May 17, 2019

The default back-button trigger navigates to the last-viewed slide instead of the actual previous slide in the scene/project. As a designer, I expect the back button to navigate to the actual-previous slide in the scene/project.

Is there a user experience guideline about navigation or is this purely preferential?

9 Replies
Jopney Test Sotomayor

Hi Taher,

The behavior you are encountering with 'back/previous' button where you are being taken to the previously viewed slide is by design. It is expected that the order will not be sequential or linear for this button.

Here's an old thread that tackles this same question and the only workaround, for now, is to manually customize the player trigger.

You just need to select the exact slide you want to show when a user clicks the 'previous' button.

 

I hope this helps.

-Jop

Taher M

Thank you for your response, Jopney Lein Sotomayor!

I read through the article you shared. Like most users, I agree hard coding triggers on each slide is frustrating. What I am curious to learn is whether there are any eLearning guidelines about the back button behavior (previous vs. last-viewed slide). If I remember correctly, the back button in other authoring tools navigate to the previous slide.

Jopney Test Sotomayor

Hi Taher,

I scanned through Articulate documentations and did not found an article discussing the specifics of the 'Back' button. What's for sure though is that this is a sound topic from the community so I suggest you to drop an enhancement request here to make this feature a more prominent request from the community to the product team.

-Jopney

Leslie McKerchie

We do have a feature request we are tracking that would allow you to set the logic for the previous slide trigger.

I've added this conversation to the report as we continue to track user impact and so that we can share any updates with you here.

I wanted to share some information about how we manage these feature requests as that may be helpful.

This discussion is closed. You can start a new discussion or contact Articulate Support.