I wouldn't put the previous button at the top unless it was at the bottom also. If it's not at the bottom, users will have to scroll up again which is counter-productive. Also, the 'Previous' button may be out of the user's sight.
You may be right about not having it beside it though. Maybe below the 'Next' button so it doesn't look so much like a set of choices with the same value but rather a list of actions in order of importance and flow. On Tue, Sep 16, 2008 at 11:26 AM, Matthew Nish-Lapidus <[EMAIL PROTECTED]>wrote: > Maybe the problem is assuming the "Previous" button has to be anywhere > near the "Next" or "Submit" button. Maybe put the "Previous" button > at the top? or at the very bottom? Maybe it's not a button at all, > but a text link or a graphical link of some sort... > > That way the submit button is in the proper place, on the left > directly below the form, but it doesn't break the conceptual right > hand paging. > > On Tue, Sep 16, 2008 at 11:21 AM, Brett Lutchman > <[EMAIL PROTECTED]> wrote: > > Having conducted multiple studies and tests on this very process, the > 'Next' > > button must be on the left side while the 'Previous' button needs to be > on > > the right. > > There are several reasons as to why this is but I will focus on the 2 > main > > ones. > > > > 1. One thing I hate when entering serial numbers for a new software is > when > > I have to manually press the 'Tab' button rather then the cursor > > automatically 'tabbing' to the right. Many developers who are sharp > enough > > to pick up on this have automated the process. This being said, some > > developers have automated the process to 'tab' to the next button or > field. > > If the last field that precedes the 'Next' button is completed, the > 'Next' > > button is the most logical action and feature in regards to keeping a > > consistent flow for the user to complete the task at hand. There is > nothing > > more aggravating then having a process flow being interrupted. > > > > 2. Users who are Net savvy tend to be quick with their left pinky finger > > (for 'Tab') their right pinky finger (for 'Enter') followed by their > right > > then left thumb with both pointer fingers locked on the 'F' and 'J' > buttons > > for bearing. > > These users who use the keyboard extensively rather then relying solely > on > > the mouse know how to rip through form fields using the 'Tab' and Space > Bar. > > If the cursor does not automatically tab to another field upon completing > a > > previous field, the user rapidly 'Tabs' with the left pinky finger and > has > > adapted to a learned behaviour. Upon reaching the first button in order > > after completing all required fields, the user is still in 'Tab' and > Space > > Bar mode and will automatically Tab to the button and hammer the Space > Bar > > to proceed with the task. > > > > Placing 'Previous' before the 'Next' or 'Submit' buttons breaks user flow > > and I strongly recommend against it. > > > > > > > > On Tue, Sep 16, 2008 at 10:31 AM, Matthew Nish-Lapidus <[EMAIL PROTECTED] > > > > wrote: > >> > >> However, if the options are "Next/Submit" and "Previous" it does make > >> more sense conceptually to have the back button on the left and the > >> next button on the right. > >> > >> The tab order, a very important piece of form design, can always be > >> manipulated to put the buttons in the right order. > >> > >> On Mon, Sep 15, 2008 at 11:21 PM, Robert Hoekman Jr <[EMAIL PROTECTED]> > >> wrote: > >> >> > >> >> In such situations is it better to have the secondary action, 'back', > >> >> to > >> >> the > >> >> left or the right of the primary action, 'next'? Or is there a better > >> >> solution? > >> >> > >> > > >> > Haven't seen any studies on this, but I provide an edge to those who > Tab > >> > their way through forms by putting the primary action button on the > left > >> > (in > >> > Western world designs anyway) so that it's first in the tab order. The > >> > options are the same regardless, and there's an advantage to giving > >> > savvier > >> > computer users a slightly easier time. > >> > > >> > -r- > >> > ________________________________________________________________ > >> > Welcome to the Interaction Design Association (IxDA)! > >> > To post to this list ....... [EMAIL PROTECTED] > >> > Unsubscribe ................ http://www.ixda.org/unsubscribe > >> > List Guidelines ............ http://www.ixda.org/guidelines > >> > List Help .................. http://www.ixda.org/help > >> > > >> > >> > >> > >> -- > >> Matt Nish-Lapidus > >> work: [EMAIL PROTECTED] / www.bibliocommons.com > >> -- > >> personal: [EMAIL PROTECTED] > >> twitter: emenel > >> ________________________________________________________________ > >> Welcome to the Interaction Design Association (IxDA)! > >> To post to this list ....... [EMAIL PROTECTED] > >> Unsubscribe ................ http://www.ixda.org/unsubscribe > >> List Guidelines ............ http://www.ixda.org/guidelines > >> List Help .................. http://www.ixda.org/help > > > > > > > > -- > > Brett Lutchman > > Web Slinger. > > > > > > -- > Matt Nish-Lapidus > work: [EMAIL PROTECTED] / www.bibliocommons.com > -- > personal: [EMAIL PROTECTED] > twitter: emenel > -- Brett Lutchman Web Slinger. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
