Issue Summary

Additional content that becomes available on hover does not allow the user to move the pointer over that same additional content without the additional content disappearing.

Element name: The following tooltips
-Show Open Issues
-Show Attributes
-Show Graph
-Object Type: Servers

Location: Below the heading "Object Overview".

Tested URL

https://instenv-5971-nizh.instenv.atl-test.space/projects/JSM/queues/custom/31/JSM-111

Steps to Reproduce

1. Step 1

Actual Results

Actual results

Expected Results

Fix Information
RULE :
The name, role, value, states, and properties of user interface components MUST be programmatically determinable by assistive technologies.

HOW TO FIX:
Fix this issue by using one of the following techniques:
1. Use the HTML <a> element. (Be sure to include an href attribute even if javascript event handlers are used.)

<a href="https://deque.com">Deque Systems</a>
<a href="javascript:void(0);">Quick view</a>

2. Use the ARIA role="link" on the custom link element container (e.g. <p>, <span> or <div>). (Be sure to use event handlers that can be operated by keyboard and touch screens.)

<span role="link" tabindex="0" data-href="https://deque.com">Deque Systems</span>

REFERENCE:
Deque University: https://dequeuniversity.com/class/semantic-structure2/links/designate-links-correctly
W3C HTML5 Recommendation: https://www.w3.org/TR/html52/textlevel-semantics.html#the-a-element

BACKGROUND:
Every user interface control must have a role to convey what type of control it is for screen reader and other assistive technology users. Native HTML elements - such as <button>, <a>, <input>, <select> - already have a role, so nothing more needs to be done. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant role(s) using ARIA as well as expected keyboard interactions.

Screenshot

Screen Recording

screen recording

Workaround

workaround

Bug Ref: 750103

Bulldog Ref: JSMDC-12601