Notes • 3 min read
Hover as a promise
A small navigation dock, and why a hover state is a promise the interface has to keep before the click ever happens.
Hover for a name, click an icon to open it, or tab through with the keyboard.
A hover state is the interface making a promise: this is clickable, and here is what it does. The tooltip is the fine print. Neither should arrive late — a label that pops in half a second after the icon already registered just reads as lag, not information.
The trick with a row of icons is that the promise only needs making once. Move from one to the next and the interface already knows you are exploring, not guessing — so the second and third tooltips should appear instantly, with only the first one pausing long enough to filter out an incidental pass of the cursor.
None of it replaces the label for someone who cannot hover at all. A screen reader gets the same name from the button itself, a keyboard user gets the same tooltip from focus, not just the mouse. The hover is a convenience layered on top of something that already works without it.