Anti-affordances also need expression

What it is

An anti-affordance means an action currently cannot, must not, or should not be performed. Interfaces should communicate unavailable actions and their reasons as well as available actions. Otherwise appearance, placement, or past experience invites clicks, drags, or submissions that the system will not accept.

Why it happens

People infer possible action from visual cues, location, and prior patterns. If a control looks usable but permission, data state, network, or workflow blocks it, people build the wrong action model and probe repeatedly. Clear constraints prevent futile attempts, explain dependencies, and point toward recovery; excessive hiding can make users unaware that a function exists.

Studying it

Test whether people can tell an action is unavailable, understand why, and find a recovery path. Record invalid attempts, repeated clicks, help seeking, incorrect explanations, and recovery time. Compare disabled, hidden, alternative-entry, and explanatory-feedback variants for reduced misunderstanding, not merely fewer clicks.

Where it stops holding

Not every limitation should be permanently visible: sensitive permissions, security, or irrelevant features may be hidden. Disabled state cannot be the end of the design; where users need the task, show when it becomes possible or how to satisfy the condition. Colour alone excludes some users.

Applying it

• For visible but currently unavailable critical actions, use recognisable disabled state and a short reason, with a route to satisfy the condition where appropriate.
• Do not make non-clickable elements perfectly mimic active controls, and do not express state with low-contrast grey alone.
• Check that people understand the constraint rather than assuming the system broke, and that keyboard and screen-reader users receive status and reason too.

Related

• Same group: B2.01.1 Affordance is a relation between object properties and user capabilities · B2.01.2 Existence of an affordance differs from noticing it · B2.01.4 Screen affordances are learned rather than physical
• Nearby: B2.02 Perceived affordance · B2.03 Signifiers
• Search terms: anti-affordance · disabled state · constraint feedback