Re: Best approach for meeting Success Criterion 1.4.13 Content on Hover or Focus via ESC key

I have written a short piece on what I see as the 1.4.13 Content on Hover or Focus dismissible problem here https://accessuse.eu/en/blog-post-en/what-is-the-best-way-to-dismiss-content-on-hover-or-focus.html <https://accessuse.eu/en/blog-post-en/what-is-the-best-way-to-dismiss-content-on-hover-or-focus.html>
The site has not quite officially launched yet but I welcome comments so I can style them :)
Maybe Steve Repsher can weigh in? If memory serves, he wrote the understanding text for 1.4.13.

> Am 25.08.2018 um 11:40 schrieb Alastair Campbell <acampbell@nomensa.com>:
> 
> > That script relates to Heydon’s toggletip,  not the tooltip -  i.e. one that is triggered not by focusing/hovering, but by activation. Still not sure whether it therefore can apply in quite the same way to true hover/focus content. 
> 
> We need to separate ‘true hover’ into two:
> 1. Hover from CSS
> 2. Hover from JavaScript
> 
> In general you can only close something with JavaScript that was opened with JavaScript.
> 
> Patrick and I discussed this on twitter a bit:
> https://twitter.com/alastc/status/1032200444259516416?s=21 
> 
> I guess it might be possible to create a function that detects anything that in in a CSS-focused state, but I don’t think it would be able to undo the action that the CSS created.
> 
> However, the general conclusion is that use of CSS-only hover (or focus-within) fails 1.4.13.
> 
> I don’t think that’s a bad thing, CSS-only drop-down / hover menus tend to fail on multiple SC already.
> 
> Cheers,
> 
> -Alastair