tags:

views:

134

answers:

8

Hi, I'm having an argument with a co-worker, and I'm trying to convince him that it's a bad idea to change checkbox text (label) according to the checkbox state.

For example, we have a combobox that automatically picks selected value (and is disabled) when checkbox next to it is checked and is enabled when checkbox is cleared. His idea is to show Autoselect when checkbox is checked and Manual select when it's cleared. I'm sure that this will confuse the user as users tend to think that checking a checkbox next to a verb will make it true, only to find that the label has changed to something else.

What is your opinion on this matter?

P.S. I remember reading about changing checkbox text somewhere, in a book or blog article, but can't remember where. It would be great to have this in writing :-)

+1  A: 

Personnaly i would say that the label shouldn't change.

MMM
+8  A: 

No need to mess with something that already works.

Changing the label would be horribly confusing and counter-intuitive, especially in the way you describe.

If the label describes the current state ("Manual select"), it will not be clear whether it is necessary to click on the checkbox to achieve the described state (like with a button), or whether it already is in that state.

A checkbox is a simple thing. When it is off, it does A. When it's on, it doesn't do A. The label needs to reflect what it does when it's turned on; it is then perfectly clear what doesn't happen when it is turned off.

Pekka
I think it's better to say: When it's "on" it does A, when it's "off" it just doesn't do A. That's why changing "A" to "B" when it's "off" is confusing.
Ilya Boyandin
I agree wholeheartedly. +1. A similar issue arises often in apps that I use with toggle buttons (basically a glorified checkbox, now that I think about it), where they change the button to say what will happen the next time you click it, rather than the current state. Both of those are confusing, but have a strange sort of logic to them. The best way is to always keep the same text and dodge the issue entirely.
rmeador
@Ilya good point, I changed the wording accordingly. @rmeador I agree, there may be an inner logic in such buttons but you need to *think* to figure it out, and that is poison for a UI.
Pekka
A: 

The label definitely shouldn't change. It's not only confusing, but it's unnecessary and ugly.

The only way I can think to make it less confusing would be to have the label state in brackets the current state, i.e. "Manual(currently auto)[]".

But that's really just a testiment to how ugly it gets.

Don't mess with what people are used to. Especially when you consider that if you do this, one will always be shown WITH a checkmark, and the other WITHOUT. Really confusing.

In the name of compromise, you COULD use a button instead, which toggles the control back and forth, and changes its value with each click.

Current mode: [Manual]

Still kind of confusing though. As I said, don't mess with what people are used to. It's like if you put a scrollbar on the left of the screen. It'll just mess with peoples' heads.

Douglas
+1  A: 

From my experience changing the text is confusing, I have the same issue with modal buttons that change their text. It is hard to tell whether pushing the button will turn on the selected state or the text is the selected state.

Tick box text should not change.

Mex
+1  A: 

Changing the text when the checkbox is checked changes the meaning. If it's checked and the label says Autoselect, I expect the Autoselect option to be enabled. If you uncheck, it's clear that the Autoselect option is NOT enabled. If you change the text to be Manual select whenever the checkbox is cleared I would expect that checking the box would enable the Manual select option. It's way too confusing if the text keeps changing.

You're right, he's wrong.

TLiebe
+3  A: 

If you want to show that the choice is between "Auto select" and "Manual select" then you should either reword your checkbox label or have a radio button:

o Manual Select  
* Auto Select

Which isn't really ideal either.

But you shouldn't be changing the text on the label - the user won't remember what it was before and will be confused when it changes.

ChrisF
A: 

I would not change the checkbox label... I would have it say "automatic." But, depending on what your controls are actually doing, I might modify the selection in the grayed-out combo-box to reflect that it is now under automatic control.

Then to make the logic go both ways, if while the checkbox was unchecked, the user selected the "automatic" value in the combo-box, the checkbox would then become checked.

Or in another scenario:

If, when the "automatic" checkbox is checked, the automatic logic actually chooses a default value that is in the combo-box, then change the selection in the combo-box to show what the automatic setting actually is. The combo would not be editable, but it could be used to provide information about the actual setting that is being engaged.

HotOil
+1  A: 

Checkbox labels should not change. That's part of the way checkboxes work.

See Should “toggle buttons” show what they do or the system status? on UXExchange for an alterantive approach using toggle buttons instead of checkboxes.

Bennett McElwee