Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I showed someone a demo of my line of business (add customer, add invoice etc) type app last night, and they provided me some feedback. Their biggest point of concern was how to navigate to the next field/textbox. They tried enter and arrow down/up. Neither worked. I told her she had to press tab and shift-tab.

She'd never heard of tab. This came as a big surprise to me.

She was very strong in her criticism, insisting that enter or down arrow are the 'standard'. It's easy enough to code, but it will introduce some inconsistencies, like 'when keyboard focus is on a dropdownlist, the down arrow will change the selected item, rather than move to the next field'.

In your experience is enter and/or arrows a common way to navigate between fields? What, if anything, is the standard behavior?

share|improve this question
1  
Your user clearly spent too much time in front of word-processors. Enter and down-arrow take you down there. Is she the only person to use the system? –  Izhaki Sep 5 '13 at 23:09
    
She's the only person I've demo-ed it to. You may be right about the word-processor thing. She has a lot of experience in the industry I'm targeting, and has used 3 of the 'big 4' applications in it. –  ausgeorge Sep 5 '13 at 23:32
1  
I was asking more to see if implementing non-conventional features such as Enter and down-arrow when possible won't put off other users. –  Izhaki Sep 5 '13 at 23:36
    
I agree with Izhaki, there is a big difference between using a computer mostly to enter text and using it for data entry filling out forms. Using enter and down arrow for navigation will be counter-intuitive for any user with more data entry than word processing experience. Especially as in data entry, enter equals the "submit"/"save" button. It will come as a surprise for many data entry people that enter doesn't submit the data they entered. Yes the enter button has a that name for a reason... :-) Enter ~ submit since time immemorial. –  Marjan Venema Sep 6 '13 at 12:11

4 Answers 4

I've got users requesting the same feature. Those users come from a background where they've worked a lot with spreadsheets.

Tab is the standard key to move focus from one field to the other.
Giving the same feature with Enter can be confusing, as the Enter button is used to trigger the default "submit" button on your form.

To convince my users that their request is not mainstream, I showed them a form on their target platform, and showed them that Enter / Down arrow does not change the focus, tab does.

share|improve this answer
    
Good call on the spreadsheets thing! –  Koen Lageveen Sep 9 '13 at 20:34

The Lift Contractor

Imagine you are a contractor who won a bid to install the lift in all branches of a new international bank. You fly across the world to meet with local representatives of your client.

Japan

A photo of lift buttons without the number 13

As you reach Tokyo where the client representatives have a rather odd request: They want the lift buttons not to have the number 13 - it's bad luck.

What would you do? Tell the client to man up and stop being superstitious, or do as they wish?

Imagine that you pick the latter - and install the lift with no 13. One day the lift breaks. Not working. Is that a problem?

France

In France, turns out that the head of operations is a Japanese, he has the same request. You go and ask other stakeholders and no one seem to mind, respecting their Japanese colleague beliefs.

What would you do?

Sweden

In Sweden, another Japanese stakeholder requests the same thing, but it turns out that in Sweden floor 13 is always the dining hall - so the Swedes really dislike the idea since it can cause much confusion.

What would you do?

The UX designer

There's a few things to learn from this story:

  • The conventions we implement in system should be those of the prospect users, not ours or those of the rest-of the world. If in Japan they use Ctrl+Alt+B to jump between fields, that's what you should give them.
  • Usability should precede consistency. It's better to have a usable system that is inconsistent than a consistent system that is unusable.
share|improve this answer
    
I don't disagree with much of that, but I don't not sure how much faith I can put in one tester's feedback. I don't think making them use Tab is "unusable". –  ausgeorge Sep 6 '13 at 0:26
    
You are correct - clearly you will have a better take on the whole issue with more user testing. Regardless, no one said anything about not not using Tab, it's really about whether or not to allow Enter and Down-arrow to do the same thing when possible. –  Izhaki Sep 6 '13 at 0:30
    
My current plan is to implement Enter the same as Tab. I don't like down/up arrows, though. Gut feeling. The problem with using Enter, though, is as Poyi said - sometimes Enter submits the form. –  ausgeorge Sep 6 '13 at 1:12

I can believe down arrow but I've never heard of Enter + arrow key combo. Enter is usually tied to the submit button, and therefore I don't think you can even do a enter + down arrow combo to skip to the next field unless you disable the enter. Tab is definitely one of the standard ways to navigate between fields. My recommendation is to convince your client that enter doesn't work or maybe settle with arrow key as well as tab or to allow all keys mentioned to navigate between fields.

share|improve this answer
    
Cheers. Just to clarify, I meant enter OR arrow (rather than enter+arrow) –  ausgeorge Sep 5 '13 at 23:29
    
ah, I was wondering where the enter + arrow came from, guess I read it wrong. best of luck. –  Poyi Sep 5 '13 at 23:41

I think we are disregarding something he said that was incredibly important.

She's the only person I've demo-ed it to. You may be right about the word-processor thing. She has a lot of experience in the industry I'm targeting, and has used 3 of the 'big 4' applications in it.

She is one of the stakeholders who'll be using this application, which means, most of the people (possibly) will be doing the same thing.

I suggest you test this with other people within your user base to understand fully what they want out of this application. Because honestly the "norm" is really tailored to what you're targeting.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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