User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it appropriate to have a single checkbox on its own? For example, if a user has the option to select an existing employee from a drop down or to create a new employee, I want to add a checkbox next to the "create new employee" option which will trigger the new employee data fields.

I know the standard is radio boxes if only one option is selected, but does the same hold true if there is only one option to select from? Hope this makes sense.

share|improve this question
Can you show us an example of what this interface would look like? – Majo0od Dec 5 '13 at 19:43
Probably you don't need neither radios nor checkbox, just place command link "New employee". – Alexey Kolchenko Dec 5 '13 at 19:46
I don't think Radio buttons should be used for "yes/no" scenarios. (though some do put two radio buttons in their UI's, one for yes, one for no). Checkboxes by their very nature are for yes/no scenarios. – BadFeelingAboutThis Dec 5 '13 at 19:47
@LDMediaServices: How would you know that the user explicitly answered "No" if a single checkbox is unchecked? Sometimes it can be useful to have Yes/No answers, where none are pre-selected. It gives you a third implicit option. IMHO/IMHE, checkboxes are designed for "I agree on this"-situations. And they are not suitable for "I disagree by leaving it unchecked"-situations. (It totally depends on the context, and what you need for your data collection.) – Jørn E. Angeltveit Dec 5 '13 at 22:45
@JørnE.Angeltveit very valid point. – BadFeelingAboutThis Dec 6 '13 at 17:03
up vote 6 down vote accepted

If I've understood your question, I don't think a checkbox is appropriate here, but not because there is only one of them. It would make sense to have a single checkbox if it can be interpreted as on/off, true/false, enabled/disabled, etc. In this case, it sounds like you would be using it to initiate an activity ("create new employee"), which is a separate flow from selecting an employee. A button or link would be more intuitive.

share|improve this answer
Agreed. That's a huge thing about a checkbox. – Majo0od Dec 5 '13 at 19:47

It doesn't make sense.

You have two options, mutually exclusive, one of which must be chosen (that is, either select an existing employee, or create a new one). That's a radio-button scenario. Or, put <Add New Employee> in the dropdown and use that to make the choice. In that case, how the dropdown is labelled becomes important.

With the radio buttons, one must be pre-selected: that should be the "Select existing employee" option. If the user chooses the other option to add a new one, that's the equivalent of checking your checkbox. It's also the same number of clicks (one).

Using a checkbox indicates that adding a new employee is available to be chosen, but it should not disable selecting an existing one — that's not how checkboxes are supposed to work. That's obviously nonsense in your situation: you need the user to make the choice between existing or new.

share|improve this answer

Your Answer


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.