---
title: "Tooltip Components Should Not Exist"
url: https://daily.dev/posts/tooltip-components-should-not-exist-joejlkbuv
source_url: https://tkdodo.eu/blog/tooltip-components-should-not-exist
type: article
source: "TkDodo"
author: "Dominik D"
published: 2025-11-17T18:31:08.255Z
updated: 2025-11-18T15:00:11.054Z
tags: ["webdev", "react", "architecture", "ux", "accessibility"]
reading_time: 5
upvotes: 42
comments: 5
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tooltip Components Should Not Exist

**[TkDodo](https://daily.dev/sources/tkdodo)** · [@tkdodo](https://daily.dev/tkdodo) · 5 min read · 42 upvotes · 5 comments

## Summary

Standalone tooltip components in design systems often lead to accessibility problems and inconsistent user experiences. The core issue is that low-level tooltip components allow developers to attach tooltips to non-interactive elements, breaking keyboard navigation and creating unpredictable UX patterns. Instead of exposing a generic Tooltip component, design systems should provide higher-level pattern components like IconButton with required titles, InfoIcon components, and InfoText elements that enforce accessible, consistent tooltip behavior by design. This restrictive approach ensures keyboard interactivity, visual discoverability, and proper accessibility labeling while preventing common misuse patterns.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://tkdodo.eu/blog/tooltip-components-should-not-exist>

## Community discussion

Top comments from developers on daily.dev.

**@michaelmastrucci** · 2 upvotes

> I agree with this article as I'm not sure I see the issue with a tooltip overall unless you either use it like a moron (a wrapper around everything?) or just overuse it period (you get a tooltip, you get a tooltip, everyone gets a tooltip!).
>
> More specifically; not giving users a visual cue (like an info icon next to the element needing said tooltip) or a way to solidify familiarity throughout your app or site (like Sentry's use of dotted underlined text from the article) just means someone has rather poor design sense or you just don't know how to properly implement them?

**@soluml** · 0 upvotes

> This largely makes sense to me. I think a Tooltip that accepts children carte blanch would end up being problematic. Forcing the Tooltip component to specify a button/anchor target with relevant a11y props is the way to go.

**@talic19** · 0 upvotes

> While I agree that generic tooltip components can be problematic, I think tooltips are very useful when a button is disabled for multiple reasons. Without a tooltip, users are left guessing why they can’t proceed. In that case, the tooltip adds clarity instead of confusion.

## Similar posts on daily.dev

- [Fixing my tooltip accessibility mistake](https://daily.dev/posts/fixing-my-tooltip-accessibility-mistake-xabm2iz7t) · Jake Archibald · 7 upvotes · 0 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#architecture](https://daily.dev/tags/architecture), [#ux](https://daily.dev/tags/ux), [#accessibility](https://daily.dev/tags/accessibility)

[View this post on daily.dev](https://daily.dev/posts/tooltip-components-should-not-exist-joejlkbuv)