Affordance
An affordance is a property or cue that suggests how an object or interface can be used.
In interface design, familiar shapes, labels, states and conventions help users recognize actions such as clicking, dragging, entering text or expanding content.
Cues that suggest how something can be used
In interface design, familiar shapes, labels, states and conventions help users recognize actions such as clicking, dragging, entering text or expanding content. In practical terms, Affordance belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.
A control that looks pressable or editable
A button that looks pressable and a text field with a clear boundary signal how those controls can be used.
Where interaction should be self-evident
You do not need to memorize the term in isolation. It becomes useful when you can recognize it in the tool, browser, file or conversation where the concept is doing real work.
Affordance is not just visual styling
An affordance is a property or cue that suggests how an object or interface can be used. By contrast, Usability describes how effectively, efficiently and satisfactorily people can use an interface to achieve intended goals. The two can appear in the same project, but they describe different parts of the work and should not be used as interchangeable labels.
The mistake: making controls look like plain text
The common mistake is to use Affordance as if it also meant Usability. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Do not rely on convention-breaking visuals when the user must guess whether an element is interactive.
Why users should not have to guess
In day-to-day work, Affordance matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.
A button that looks pressable and a text field with a clear boundary signal how those controls can be used. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.
Related terms worth learning next
Sources and further reading
Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.