> For the complete documentation index, see [llms.txt](https://ebay.gitbook.io/mindpatterns/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ebay.gitbook.io/mindpatterns/antipatterns/non-interactive-hover.md).

# Mouse Hover on Static Elements

Do not add mouse hover behaviour to static text and icons. The behaviour will not be fully accessible to keyboard and screen reader users.

To "workaround" this issue, a common mistake is for a developer to add tabindex="0" to the static element in order to make it "keyboard accessible"; however the problem is that static elements have no implicit role that programmatically connects the element to the additional content or behaviour.

The classic example is misuse of the tooltip pattern. Tooltips are used to provide information about *interactive* elements (such as buttons) - yet we often see designs that try to apply them to static text and icons.

**See also**: [Tabindex-itis](/mindpatterns/antipatterns/tabindexitis.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ebay.gitbook.io/mindpatterns/antipatterns/non-interactive-hover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.