A button’s resting appearance is only one part of its design. Focus, hover, disabled, and busy states help explain whether the action is available and what is happening when someone uses it.
Keep the label and the behavior coherent. If an operation takes time, show that it has started and avoid making the person guess whether another click is needed. A visible focus indicator helps keyboard users locate the current action.
Try the full sequence with the input methods the interface supports. Notice whether the control stays understandable while busy and whether completion is confirmed elsewhere on the page. The state belongs to the whole interaction, not only the shape of the button.
An example to consider.
Imagine a keyboard user reaching a button without pointing at it. Its focused appearance is a working state that deserves the same care as its ordinary view.
Put it in perspective.
Follow a person through the awkward middle of a task. Their progress, choices, and recovery matter as much as the finished state.
- Review focus and busy states.
- Confirm that an action has started.
- Make the resulting change visible.
Follow a related question
Name the audience and intended effect.
A brief that leaves room for an ideaKeep a small current entry point.
A reading list with an entry pointKeep learning
Related background to continue exploring this subject.
W3C: understanding accessibility criteria MDN: responsive images
