A component that displays informative text when users hover over or focus on an element.
Tooltips provide brief, context-sensitive information that appears when a user hovers over or focuses on an element. They help users understand icons, buttons, or form fields by offering additional details without cluttering the interface.
Aspect | Best Practice |
---|---|
Usage | Present supplementary details or clarifications for a UI element. Tooltips appear on hover or focus and disappear when the user moves away. |
Visual Hierarchy | Position tooltips near the related element, ensuring they don’t obstruct main content. They should feel like a natural extension, not an interruption. |
Behavior | Triggered by hover/focus and dismissed when the user moves away. They’re non-intrusive, context-sensitive, and should enhance—not disrupt—workflow. |
Psychological Impact | Provide on-demand information to enhance understanding without forcing navigation away or cluttering the interface. |
Examples | Explaining an icon’s function or providing formatting guidelines for a form field. |
Use sentence case and proper punctuation for consistency and readability.
Write in active voice, using simple, clear language.
Avoid jargon; if needed, define unfamiliar terms.
Keep tooltips concise and focused on adding genuine value.
Ensure accessibility by making tooltips keyboard navigable and screen reader friendly. Refer to ARIA guidelines and follow best practices for inclusive design.
See: Blazor Telerik UI for Blazor Tooltip Documentation | Tooltip Accessibility
For technical details and integration guidance:
Tooltips provide brief, context-sensitive information that appears when a user hovers over or focuses on an element. They help users understand icons, buttons, or form fields by offering additional details without cluttering the interface.
Aspect | Best Practice |
---|---|
Usage | Present supplementary details or clarifications for a UI element. Tooltips appear on hover or focus and disappear when the user moves away. |
Visual Hierarchy | Position tooltips near the related element, ensuring they don’t obstruct main content. They should feel like a natural extension, not an interruption. |
Behavior | Triggered by hover/focus and dismissed when the user moves away. They’re non-intrusive, context-sensitive, and should enhance—not disrupt—workflow. |
Psychological Impact | Provide on-demand information to enhance understanding without forcing navigation away or cluttering the interface. |
Examples | Explaining an icon’s function or providing formatting guidelines for a form field. |
Use sentence case and proper punctuation for consistency and readability.
Write in active voice, using simple, clear language.
Avoid jargon; if needed, define unfamiliar terms.
Keep tooltips concise and focused on adding genuine value.
Ensure accessibility by making tooltips keyboard navigable and screen reader friendly. Refer to ARIA guidelines and follow best practices for inclusive design.
See: Blazor Telerik UI for Blazor Tooltip Documentation | Tooltip Accessibility
For technical details and integration guidance:
For more examples, visit the Storybook.
Opens a tooltip with text content.
Opens a tooltip with custom content.
Closes the currently displayed tooltip.
Gets or sets the position of the tooltip relative to the target element. Possible values: Top, Right, Bottom, Left.
Gets or sets the duration in milliseconds that the tooltip remains visible. If null, the tooltip will remain visible until explicitly closed.
Gets or sets the delay in milliseconds before the tooltip appears.
Gets or sets whether the tooltip closes when clicking anywhere on the document.
Gets or sets additional inline CSS styles for the tooltip.
Gets or sets additional CSS class(es) for the tooltip.
Gets or sets the text content of the tooltip.
Gets or sets the custom content of the tooltip.