Affordance

What is an Affordance?

An affordance is the relationship between an object and a user that makes a particular action possible: a chair affords sitting, a door handle affords pulling, a scrollable list affords scrolling. The term was coined by the psychologist James J. Gibson in 1979 to describe what an environment offers an animal, and Donald Norman brought it into design in The Design of Everyday Things (1988), where it became shorthand for "the parts of a design that tell you what you can do with it". Norman later refined his own usage: the affordance is the possibility of action (the button can be pressed), and the signifier is the perceivable cue that communicates it (the button looks pressable). Most interface problems described as "poor affordance" are signifier problems: the action exists and nothing tells the user so.

Affordances in Interfaces

Perceived affordances. On a screen, everything is pixels, so the affordances that matter are perceived: the shadow that says pressable, the underline that says linkable, the handle that says draggable, the cursor change that says interactive. Design conventions accumulate into a shared language of signifiers, which is why consistency with platform patterns matters and why novel controls need teaching.

Hidden affordances. Gestures, long presses, keyboard shortcuts, and hover states are real affordances with weak or absent signifiers; they reward experts and are invisible to everyone else. The rise of flat design made this a recurring problem, as decorative cues that had signaled interactivity were stripped away.

False affordances. Things that look interactive and aren't: underlined text that isn't a link, a card that looks tappable and does nothing. Each one costs a click and a little trust.

Anti-affordances and constraints. Signifiers that say "you can't": the grayed-out button, the disabled field, which communicate state as much as possibility.

Finding the Missing Ones

1. Watch for hesitation and hunting.
In usability sessions, the participant who hovers, hesitates, and then tries something else has met a missing signifier; the recording shows exactly where. Unmoderated sessions with narration ("I'm not sure if I can click this") make the failure audible.

2. Use first-click and five-second tests.
First-click tests reveal what people believe is interactive; a five-second exposure followed by "what could you do on this screen?" reveals which affordances were perceived at a glance.

3. Compare against users' mental models.
Affordances are read through expectation; a control that works like the user's model of similar products needs less signaling than a novel one. Research on what patterns the audience already knows tells you where signifiers can be light and where they must be loud.

4. Audit with heuristics.
An expert review against visibility and consistency principles catches false and hidden affordances quickly, before participants' time is spent on the obvious ones.

5. Test with the audience that matters.
Signifier conventions differ by platform, age, and experience; what affords tapping to a teenager may not to a first-time smartphone user, and accessibility adds the requirement that affordances be perceivable without sight or fine motor control.

The Bottom Line

An affordance is what an interface lets you do; a signifier is how it tells you. Most "affordance" failures are missing, hidden, or false signifiers, and they are found by watching people hesitate, testing first clicks and first impressions, comparing against users' expectations, auditing with heuristics, and testing with the real audience. If users can't tell what's possible, the possibility might as well not exist.