Affordance

An affordance is a property of an object that indicates how it can be used. The term originates with psychologist James J. Gibson and was adapted for design by Don Norman, who later refined it to distinguish real affordances from perceived ones. In interface work, the distinction that matters is between what an element can actually do and what a person believes it can do: a button that looks clickable and is clickable has a matched affordance, while a heading styled to look like a button creates a false one.

Digital interfaces have no physical affordances, so every cue is a learned convention rendered visually. Raised or filled shapes suggest pressing. Underlined colored text suggests navigation. Input fields with borders suggest typing. Handles at the corner of an area suggest resizing. Cursor changes on hover confirm interactivity. None of these is inherent; they are all conventions accumulated over decades of software use, which is why departing from them imposes a learning cost, and why the conventions themselves are worth respecting even when they are aesthetically unfashionable.

The most consequential failure mode of the last decade has been the erosion of interactive affordances in the pursuit of visual simplicity. Flat buttons without borders or fills, links distinguished only by weight, icons without labels, and controls that appear only on hover all reduce visual noise and simultaneously reduce discoverability. On touch devices, where hover does not exist, hover-revealed controls are not merely subtle but effectively invisible. Usability testing routinely finds participants failing to notice actions that the design team considers obvious.

The reverse failure is equally damaging. Elements that look interactive but are not cause repeated failed clicks and mild frustration, and each failure teaches the visitor to trust the interface less. Common culprits include decorative cards with button-like styling, images that look tappable, and disabled controls presented without any explanation of why they are unavailable. Session recordings showing repeated clicking on a non-interactive element are one of the clearest diagnostic signals available.

Signifiers, in Norman's later vocabulary, are the perceivable cues that communicate an affordance, and it is signifiers rather than affordances that designers actually control. The practical question in review is therefore not whether an element is interactive but whether an ordinary person, arriving without context, would recognize it as such within a moment, and whether anything that is not interactive is signalling that it might be.

Disabled controls are a specific and common failure worth separating out. A control that appears but cannot be used communicates that an action exists while withholding both the action and the reason, which leaves the user to guess what condition they have failed to meet. The alternatives are usually better: hiding the control entirely where it is irrelevant, or keeping it enabled and explaining the blocking condition when it is activated, which converts a dead end into guidance. Where a disabled state is genuinely appropriate, the reason should be visible without interaction rather than hidden behind a hover tooltip that does not exist on touch devices. This pattern accounts for a surprising share of support contacts in transactional systems, since users conclude that the system is broken rather than that they have missed a prerequisite.

Because these judgments are unreliable from inside a team that already knows how the interface works, they need external verification. First click testing and moderated sessions conducted through user research expose affordance failures quickly, often on the first participant. Preventing recurrence is a systems problem rather than a page problem: defining a small, consistent set of interactive treatments within a design system during product design work ensures that interactivity is signalled the same way everywhere, so people only have to learn it once.