Interaction States and Feedback
Overview
Every interactive element can exist in more than one state: default, hover, focus, active, disabled, and loading. Feedback is what confirms to the person that their action actually registered.
Why It Matters
Without visible feedback, a person cannot tell whether a click worked, is still processing, or failed silently. That uncertainty is exactly what Nielsen's "visibility of system status" heuristic warns against: the design should always keep people informed about what is happening, within a reasonable amount of time.
Core Principles
- Five core states, at minimum. Default, hover, focus, active, and disabled are the states every interactive element needs; loading, success, error, and selected are common additional states depending on what the element does.
- Give people control and a way back. Nielsen's "user control and freedom": a clear way to cancel or undo an action in progress, not just to trigger it.
- Errors should say what happened and how to recover. Nielsen's "help users recognize, diagnose, and recover from errors": plain language, not an internal error code.
Interactive Demo
Click the live demo button to see it move through active, loading, and success states in sequence.
Common Mistakes
- No visible difference between a button's default and disabled state, so a person keeps clicking something that will never respond.
- A loading state with no time limit or fallback, leaving no way to tell a stall apart from normal processing.
- Removing the focus state for visual reasons, breaking keyboard navigation entirely for that element.
Related Concepts
- Forms and Inputs: form controls need the same state coverage as buttons.
- Motion: state transitions are often where subtle motion is most useful.
Used In Templates
Demonstrated directly in the Landing Page, Small Business and Local Service Site, E-commerce Product Page, SaaS Pricing Page, Nonprofit and Charity Site, Online Course Landing Page, Community and Forum Homepage, Newsletter and Waitlist Signup Page, and Multi-step Onboarding Flow templates; see docs/PRD.md section 13.2.
Summary
Every interactive element needs a visible state for every situation it can be in, and feedback that confirms an action registered. Without both, a person is left guessing whether the interface heard them at all.