Interface Affordances

Affordances make possible actions perceptible. If people cannot tell what they can do, the interaction is incomplete even when the code works.

Defaults

1. Visual cues must match real behaviour.
2. Critical actions cannot depend on hover alone.
3. Hit targets and spacing should match the input method.
4. State changes should explain themselves (pressed, selected, expanded, disabled, loading).
5. Decorative motion must not impersonate an affordance.

Prefer / Reject