Julia Kirschenheuter

### Conclusion It is very hard to meet all most important requirements to fulfill accessibility fulfillment. It is also hard to find a very-accessible implementation e.g. third libraries. As is...

> I think I observed that in some scenarios we do use "aria-describedby" as soon as a tooltip appears. Right connection with element via "aria-describedby" is of coarse an important...

> Without moving the pointer hover or keyboard focus – so it can **not** be an x close button like in the example. Imagine you are on a mobile device....

> On Android system, tooltips vanish when you scroll or tap anywhere (even on tooltip, or on the icon it belongs to). That sounds reasonable? i know, i'm just speaking...

I've searched for possible solutions what could we "take and integrate" and this seems not good. There are several web components library and almost all of them are not accessible....

Last status / suggestion: use a native tooltips only like small additional information in combination with other a11y tools like aria-describedby or aria-label's. This should be fine. For now not...

done for server

moving this issue to "descoped" because not relevant for now

I would say that adding invisible heading (like `` or ``) with `class="hidden-visually"` should be enough.

not relevant for now