Steps to reproduce:

1. Enable screen reader
2. Navigate to any component triggering the tooltip on focus using Tab
3. Tooltip is not being read

Expected:

Tooltips should be read automatically by a screen reader when user moves focus to the trigger component using Tab.

ARIA tooltip role overview with working example:
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/tooltip_role

WCAG violations:

4.1.2 Name, Role, Value (A) ** primary violation. If the tooltip DOM node doesn't exist until the trigger event fires, there's nothing for the accessibility tree to expose beforehand; if it's also not properly associated via aria-describedby pointing to an ID that exists at trigger time, the AT has no way to discover it at all.

1.3.1 Info and Relationships (A) — secondary, if aria-describedby is set on the trigger pointing to an ID but that element isn't created/inserted until after the reference is evaluated (common bug: AT reads aria-describedby once on initial tree build, misses the dynamically-injected node, especially if insertion happens without proper reparsing/mutation handling).

1.4.13 Content on Hover or Focus (AA)  must be dismissible (Esc), hoverable, persistent.

2.1.1 Keyboard (A) — hover-only trigger with no focus/blur equivalent.