Basics: Disable or Hide?

UX Interaction Design December 15th, 2008

Back to the basics here.  I found this topic on a recent email thread a
great reminder as to why one would disable tools or menu options versus hide them.  Of course
it always comes down to context, but the bottom line…

Disable controls that are dependent upon the currently selected tool, mode, or other selection.

Hide options that are dependent upon their permission level (E.g. administrative controls).

Of course use smart grouping and other indicators to make the reasons obvious.

Why?  Disabling…
- Indicates that the options are possible, but not during the current system state.  So therefore the user knows they need to do something else to access those tools, if that is their goal.
- Keeps all controls always visible in the same position within the same list.  This leverages visual/spatial memory and clues them that they are in the correct menu or tool set.
- Tech Support will love you, because that helps them identify the system state.  Imagine if they instruct the user to look for ‘copy’ under the ‘edit’ menu and the user says it is not there.  Tech support now does not know if the user is even in the correct screen, let alone correct state.

Comments are closed.