Hidden vs. Disabled In UX — Smashing Magazine

Basic control and flexibility that allows the user to easily go back, cancel, close, or undo is a given and should be supported in any interface. But allowing users to completely customize their experience should be reserved only for professionals or not given at all. The happy intermediary, where everyday users have enough flexibility that they’re

Almost all products need both a “novice” and an “expert” mode, but it’s important to keep in mind that power user features should always be an alternative way to use the interface—never the primary way.

Do we truly understand the user’s intent in this exact interaction? Are we hiding things that stop the user from progressing? Are there clear indicators that point to what’s hidden? Is it easy to recall the hidden features? Have we tested the interaction to ensure it works as we imagined?

Hiding anything means putting a barrier between the user and the feature,

Exactly in the area where the error occurred—in a way that draws the user’s attention—we have to explain what happened, why it happened, and what the user can do to fix it. Or if the error cannot be resolved by the user (as was the case when the New York State Department website wasn’t working at all), we have to explain to the user why the system