Affordance
An Affordance is a visible or felt clue that shows how an object can be used.
Another example
A raised shape and the word “Save” make it clear that the button can be pressed.
Main parts
- 01Foundation or token
- 02Applied component
- 03Visible state and rule
Use it when
Strengthen the clue when people pause or can't tell what they can use.
Do not use it when
If an action has an unclear result, do not rely on shape or color alone. Add clear words.
Name used in code
perceived action cue Before you ship
Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.
Outcome: Use or define Affordance to make the visual experience clear and easy to use. User context: A raised shape and the word “Save” make it clear that the button can be pressed. Design concept to apply: Affordance. Why it fits: Strengthen the clue when people pause or can't tell what they can use. Do not use it when: If an action has an unclear result, do not rely on shape or color alone. Add clear words. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.
Check this request
Review the current use of Affordance. Definition: An Affordance is a visible or felt clue that shows how an object can be used. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.