Web design and digital-business ideas grounded in real tasks.

A hover tooltip should stay open when the pointer moves onto it

A web designer testing a small generic tooltip beside an interface control on a laptop, no legible text or logos.
AI-generated photographic illustration; not documentary photography.

You move the pointer over a small help icon and a useful explanation appears. Before you can finish reading, the panel disappears because you tried to move the pointer onto it. The text existed, but the interaction made it difficult to use.

WCAG’s guidance on content shown by hover or focus describes three relevant qualities: dismissible, hoverable and persistent. These requirements apply in defined circumstances, with exceptions. They are more precise than the broad instruction to make a tooltip accessible.

Test the whole journey into and out of the help

For additional content triggered by pointer hover, a user should be able to move the pointer over that content without making it vanish. Persistence concerns keeping it available until the trigger is removed, the user dismisses it, or its information is no longer valid. A supported dismissal method should not require moving pointer or keyboard focus when the criterion requires dismissal.

Try the control slowly. Move from the trigger into the panel, pause to read, then leave. Repeat using keyboard focus. If the help covers information needed for the task, test whether it can be dismissed while keeping the user’s place. Check the documented exceptions rather than assuming every browser-native tooltip behaves like a custom component.

Keep essential instructions available elsewhere

A field’s required format should not depend entirely on someone discovering a tiny hover target. Persistent explanatory text can be a better choice for information needed by almost everyone. A touch interface also needs an intentional way to access help; the presence of a mouse-hover handler does not establish one.

For example, a fictional booking form might place its date format directly below the input and reserve optional background explanation for a help control. That reduces how much the tooltip must carry while leaving the main instruction visible.

Include enlargement and narrow layouts in the review. The useful test is whether someone can find, read and leave the explanation without losing their place—not simply whether a screenshot shows a well-designed floating box.