Accessible Tool Tips

1 Initial Problem

Tool Tips disappear one the focus is removed from the tip-triggering UI-Element.

This prevents users with magnifying assistive technology to actually read the tool tip. Their viewport is only a few letters big (think "0,5 cm section" of what you would typically see at one glance).

They have to move their viewport from the trigger to the tip's text to actually read it. But they cannot, because once their focus leaves the trigger, the tool tip stops being displayed.

2 Conceptual Summary

The respective guideline is Success Criterion Content on Hover or Focus

This is an old and difficult problem. Since 2016 there has been no progress see W3C Aria Practices Draft tooltip design pattern

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

Schmidt-Sielex, Wolfgang [WSS] 2023-07-20: Feature has been discussed by a sub-group of SIG accessibility and set to 'outdated' because there is a different up-to-date feature request of the same topic: New, accessible Tooltips. Furthermore there is a special element in the kitchen sink (KS) and the 'persisting IDs in Global Screen Services', that should/could solve the issues.

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.