I have a one page checkout where the user proceeds through an accordion type process for personal details/shipping etc which all loads via AJAX so there is no page refresh.

E.g Step 1 is personal details - you fill it in, click continue and then step 1 collapses, step 2 opens and you carry on.

My question is how should the Browser back button behave? Should it take you back through the steps (seems a little weird as it's not a page refresh) or should it take you back out of the checkout completely?


1 Answer 1


You are thinking in programmer terms rather than user terms. The way a system is implemented is of no concern for the user, and users are typically completely unaware of whether a page was reloaded or simply update by AJAX.

What you should account for is the mental model of users - if the interface appears as if it moved forward one step, most users would expect the back button to take them to them a step back.

Bare in mind that any other choice for the back button might be completely arbitrary - from a user point of view, why would the back button take you to the beginning of the checkout process and not the product page you came from? How can you tell where users would like to go to when pressing the back button? Back to previous step is the only obvious option here, more so in a checkout wizard.

There are a multitude of applications out there which make usage of ajax to load parts of the page (The source browsing in GitHub is one famous example), all use the back button to go one screen back (even if the header, footer, and other content area have not been refreshed at all).

  • Makes sense - I was leaning along those lines anyway - thanks
    – Chris
    Jan 15, 2014 at 11:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.