Tag Info

New answers tagged

4

TL;DR Based on an informal usability study conducted on a similar need (but in a different problem domain): Separate the "none of the other options" option from the list of other options. Place the two lists side-by-side, such that the most common list comes first. The "none of the other options" option should be a check box, like all the others. The ...


0

Separate the 'None of the above' checkbox from the list of checkboxes with a horizontal rule or some other separation aid. This will help the user understand that this option is a different one from the normal options present in the list. Also, I would suggest that checking this option will disable or remove all checked items from the list above. If you ...


18

Rewobs' answer is good, but it involves two levels of complexity: first clicking one of two ratio buttons, then selecting the checkboxes. The user experience of that design can be improved by simply having a visually separated None of the above box at the bottom. Someone suggested clearing the users' choices, but that is bad because accidentally checking ...


10

tl;dr Make the form behave as if the user is filling a paper sheet while someone stands beside them to nag them when they make mistakes. I'd keep your design adding real-time validation: download bmml source – Wireframes created with Balsamiq Mockups If something is not right, change the last line: download bmml source If the ...


9

Don't use checkboxes. I would try to split it into two questions: In the last 3 years, have you had any nasty illnesses? ○ yes ○ no Which ones? ○ headaches ○ colds ○ flu ○ arthritis etc. Only show question 2 once they answer "yes" to question 1. The drawback is that the user might have had a disease which isn't on your list, so they would choose "yes", ...


13

Make the "None of the above" Checkbox Clear All Others Keep the UI you have, but add a bit of JS that makes the "None of the above" (NoTA) checkbox also clear any other already-checked boxes If the user clicks just clicks on NoTA, the form behaves exactly as expected. If they click a few other options first, and then click 'NoTA,' they'll either notice ...


85

My first idea was the same as in Izhaki's answer, but later I think of this, that seems to fulfill your goal and reduces (at least a bit) the need of user interaction without drawbacks. (EDIT: thanks to @dennislees for improving the colors. If it goes well with the rest of your UI, IMO this will improve the consistency of this approach ) download ...


19

Check boxes are not ideal in your case since they are used for multi-selection (in theory, one can choose none of the above and another option - while Javascript can 'fix' this, it's not exactly obvious to users). I may not be answering your question directly, but consider this format instead: download bmml source – Wireframes created with ...


1

When it's required, and there are only two choices, a radio group makes much more sense. A radio group allows the user to quickly see the available choices and select one with a minimum of action. Whereas a drop down requires at least two clicks: one to see the possible selections, the other to actually pick something. I'm not sure why you'd think that ...


0

I prefer the checkbox, but I agree that there's some iffyness when making it required, and it's probably not wise to go with a three-state checkbox (empty, check, and box) because what does that even mean? Thinking of the SharePoint forms, there are two options for a yes/no field: Radios or Dropdown... Drop down may do the trick for you -- common control, ...


1

What you probably need if you don't want to break any conventional UI design patterns would be to first have a radio button group that allows you to decide whether you want to choose just one or have multiple selections. Then once you make the selection it toggles the behaviour of options A-D into either radio buttons or checkboxes. download bmml ...


0

Since you know there will be at most 4 per group, how about a drop down followed by a clickable hyperlink that reveals the checkboxes: download bmml source – Wireframes created with Balsamiq Mockups I feel like the change between single and multi-selection is more explicit to the user.


1

I definitely wouldn't put two different types of selection inputs on the same items. Even if the inputs respond display the correct number of selected elements based on the user's clicks, he or she will likely be confused about whether or not both methods of selecting the item is required. It would be better to just leave them as checkboxes because that ...



Top 50 recent answers are included