Tag Info

Hot answers tagged

46

There is at least a single benefit for those not using a mouse - Normally you are able to tab between input elements using the keyboard, this is an indicator as to which element currently has your focus.


41

Rather than focussing on the Z or column pattern, you might want to consider grouping related information. In your example it might be confusing for the user that Address and City are not grouped together. So you could group the name fields, the address fields (Address, City, Postal Code and Country), the contact fields (E-mail and Telephone) and lastly ...


9

After doing some reading it seems that the highlighting in fact does help the user as people have come to be reliant on the UX/UI guiding them through the page and showing where they are focusing as well. For example if a user is filling out a form and using the "tab" key to jump from area to area they want to see the focus highlight change from what they ...


8

Quite simply, you should avoid multi-column forms because people may interpret the form's flow in various ways.


5

You could add a "None of the above" option, then make the question required. You might then rephrase the question to "Which of the following areas are you or a member of your household employed?" Healthcare Manufacturing etc... None of the Above


5

I think this pattern can be called " List Entry View ". Full description can be found here, All list of patterns


5

Yes you should! Your suggestion about having a validation rule would be a very bad idea. Did you know, the world's most common last name is 王? Here is a classic article that you need to read: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ All of these assumptions are wrong: (...) People’s names are written in ...


4

Amazon's process keep you informed of both the entire process and the step you are currently completing : A suggestion could be : to inform your users at the beginning of the process and also before they start the payment that there will be another key step after that to always display an Amazon-like path and current step to send an email to your users ...


3

Ceefin's answer makes a very good point. By focusing too much on the details you can overlook what actually matters about UX, which is what the user experiences. And there's no more frustrating experience than a form that asks a simple question, then doesn't let you answer it. This kind of over-validation is horribly common with postal addresses-- I've ...


3

I would use a radio list and include "don't attach a CV" as one of the options. Don't modify the behaviour of checkboxes - that would be misleading. download bmml source – Wireframes created with Balsamiq Mockups


2

I agree with your second proposed solution (radio button being the technically the right input to use here). I also can see how those would look confusing together, especially because as I understand it, an item has to be checked in order for it to next be selected as a leader, and the two together do not represent this dependency well on top of looking ...


2

The order is more important that leading with the default. You should present the choices in the order the user expects. If a list is in the right order, the user will be able to mentally chunk it and rely on their past experiences to basically not read the entire list. If the highlighted button is near the middle or the top or the bottom they can make an ...


2

A clearly defined label stating what input is required by the user should prevent the problem of max length of the input field. There may well be people over the age of 99 using the internet now, so perhaps max length should be 3


2

U.S. Department of Health and Human Services has created and maintains a wonderful website: http://www.usability.gov. It contains a wealth of UX resources of various types, including the ones from a government organization perspective (see section "Guidance and Government-specific Resources" at http://www.usability.gov/how-to-and-tools/index.html). Hope it ...


2

You could try to group related, relevant information together and leave out mutually exclusive items. As it is a read-only format there's not a lot of use in displaying the mutually exclusive NO answers (and possibly also some other NO answers). I'd suppose that if Veteran is answered with NO all other Veteran related answers are obsolete and of no good ...


2

How about an (red) "NO" icon or a (green) "Yes" icon to the left of each line? This way you save vertical space, but at least keep visual consistency (providing that you keep both icons the same width). Is there any other solution, like filtering the results to only show the positives or negatives, if that is what the user is after? This way you'll ...


2

How many inputs should be presented on each page? And does this depend on categorisation of inputs? My thought is the grouping of the inputs is more important than the number. For example, the workflow for setting up an iOS device is divided into screens for language, Wi-Fi, location services, etc. The number of inputs for each grouping is less ...


1

The technical term for that is "Incremental Filtering". It's always hard (particularly in mobile) to show big sets of data, but IF the user is going to know who to send this to right away, for example, if the user is going to have the addressee already in mind, the expected behavior is for the user to start typing the friend's name, and this is optimum. I ...


1

I just designed multiple screens registration form in the iOS app. First we wanted to make it as single screen but then after little research I find out that it is much more comfortable for users when you split all informations in logical steps (2-3). It could be even more effective for the app developer. Let me explain. When user come to the registration ...


1

I feel that the best solution would be to use a watermark (gray text in an input when it's empty) with the text 0-99. This clearly states that: Input has to be a number The range is from 0 to 99 There are even ready-made solutions for this, like jquery-watermark.


1

I have a couple of ideas. One possibility is to embolden the placeholder text of the required ones. That may not be very intuitive but it should at least indicate that there is a difference and they may be able to then infer from the fields that those are required and the other aren't. Likewise, you could italicize optional fields. Another is to add ...


1

One idea, if applicable based on your data set and architecture, could be to have : one single quick search field using predictive typing and live refresh of search results. Your users could then start typing, say, "repl 113" and the predictive typing would suggest "replenishment" as they type the "l" (in real time during typing, so difficult to render ...


1

Best practice would be to always have the field wide enough to display short fields like names, phone numbers, and emails, without the need to wrap the text to another line. Such fields will always have a technical constraint on their length imposed by the back end (data base field), and this will be quite conservative anyway for short fields (why set up a ...


1

Picking from these two options I would prefer 2nd solution from various reasons: It's Windows application and the standard they handle entering and editing since early versions is a Save button. It means users will know how to use it and prefer not learning anything specific. In combination with TAB and keyword shortcuts it's the fastest and safest thing ...


1

One way is to show the users a message in bold text (probably even using highlighting) that the process is not completed and there is still a couple more things to be done. Secondly, if you think warning message might spook the user, you could display a progress bar at the top of the page from a step before the payment step until they complete the whole ...


1

Matt's solution seems very clear to me. However it depends on the number of CV's you are going to show them. If the person has approximately more than 5-6 CV's; I would suggest to have a selection box - combo box. I would also suggest to put the no-CV option at the checkout. I have another suggestion. selecting from a large list is something I deal with ...


1

As avi said, it shows that you're pointing to it. This is obviously useful if you're not using the mouse, as others mentioned. But it's useful even when you are using the mouse, even though there's a cursor that ideally also shows what you're pointing at. For example, if your cursor is on the edge of an element, it may not be obvious what's going to happen ...


1

After talking to our developers about what is possible with our data model, I've proposed a design similar to this: My users are only likely to change a field or two at a time, so instead of showing the entire form with 20 fields, it lets them select the field(s) they wish to edit and ignore the rest. In the event they select a conditional field I've ...


1

Bottom is definitely the most common way that I've seen it displayed, and left/right is probably just dependent on the placement of your submit/save etc buttons. You simply want to let people know when they are about to go over, or have already gone over. If they have gone over, you want to let them know how much they need to cut it down. In this respect I ...


1

The common practice seems to be to add it below. See e.g. the comment boxes on any Stackexchange site or Twitter. The important part IMHO is that the number is visible to the user when the information is relevant. E.g. if your input field is big and goes below the fold, but you want to give the user feedback to add at least 15 characters (like ...



Only top voted, non community-wiki answers of a minimum length are eligible