Do not show hover content the pointer cannot reach
A tooltip appears on hover and vanishes the second you try to move onto it, because a gap sits between the trigger and the content. F95 is the failure technique for that, so a match is a defect rather than a technique. It covers one of the three things the rule asks for, which is that hover content can be hovered. Dismissible and persistent are the other two and this technique says nothing about either. Two boundaries decide most findings. A tooltip the browser draws from a title attribute falls outside the rule, because the browser owns that presentation rather than you. And there is a second way to break it that closing the gap will not fix, where the pointer crosses another trigger on the way and the popup gets replaced instead of kept. Charts with a tooltip on every data point live in that second case.
How we find it in an audit
Every hover-revealed thing on the audited pages gets the same test, which is to move the pointer slowly off the trigger and onto the content and see whether the content survives the trip. Slowly is the point, because a fast diagonal often skips the gap a real hand will land in. Charts get walked point by point, since a popup replaced by its neighbour looks like a working tooltip right up until you need to read one. Native title tooltips get noted and set aside, because the browser owns those.
How affected users experience it
Screen magnifier users take the direct hit, since at high magnification the tooltip often sits outside the piece of screen they can see. Reading it means moving the pointer, moving the pointer moves the magnified view, and moving off the trigger kills the tooltip. So the content exists and cannot be read. Anyone with a tremor meets a smaller version of the same thing, where one wobble off the trigger loses the text and the whole approach has to start again.
Passes vs. fails
Passes
wrapper.addEventListener("mouseleave", hideTip); // wrapper holds both, so there is no gap to crossFails
trigger.addEventListener("mouseleave", hideTip); // a gap sits between trigger and tooltipThe other techniques filed under this rule
2 guides on this site are filed under 1.4.13 Content on Hover or Focus. W3C documents this one as a failure of that rule, so it describes a way the rule gets broken rather than a way to pass it.
This guide is our interpretation of W3C technique F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable. W3C publishes its techniques as guidance rather than as the standard, and says so on every one of them. The success criterion is what conformance is measured against, and a technique is one documented way to meet it.