B2.01.2Perceived affordancedesignresearch

Existence of an affordance differs from noticing it

Aliases: discoverability · action possibility · affordance

What it is

An action can be executable in a system without a user recognising it; conversely, a person can think something is clickable or draggable when it is not. The first is affordance; the second concerns perceived affordance and discoverability. Conflating them misdiagnoses “cannot do” and “did not find” as one problem.

Why it happens

Actual affordance follows event handling, permission, device, and capability; noticing depends on visual cues, language, prior experience, context, and attention. A hidden gesture may exist but remain undiscovered; decorative styling can imply a button without behaviour. The gap between system capability and mental model produces probing, hesitation, accidental action, or unused functions.

Studying it

Measure first-discovery rate, correct expectation of function, actual completion, and erroneous attempts separately. Unguided exploration, task observation, first-click testing, and interviews distinguish missed cues, misunderstood action, and technical constraint. Low click rate alone is ambiguous: it can mean no need or no discovery.

Where it stops holding

Not every capability must be immediately visible: advanced or rare functions can use search, help, or progressive disclosure. Conversely, high-risk actions may intentionally reduce surface affordance while retaining a deliberate, clear path. The target is discoverability matched to importance, not making every area button-like.

Applying it

  • For critical first-use actions, verify separately that the system can perform them, people understand them, and they can execute successfully.
  • In exploration testing, record false assumptions and undiscovered functions, then repair cues, labels, hit areas, or permission explanations separately.
  • Provide searchable, explainable fallback access for infrequent features instead of relying entirely on concealed gestures.

Related

  • Same group: B2.01.1 Affordance is a relation between object properties and user capabilities · B2.01.3 Anti-affordances also need expression · B2.01.4 Screen affordances are learned rather than physical
  • Nearby: B2.02 Perceived affordance · B2.03 Signifiers
  • Search terms: perceived affordance · discoverability · affordance

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/B2.01.2