- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 28 Aug 2018 14:30:06 +0000
- To: Detlev Fischer <detlev.fischer@testkreis.de>
- CC: WCAG group <w3c-wai-gl@w3.org>
Received on Tuesday, 28 August 2018 14:30:36 UTC
Hi Detlev, I’m not sure what you’re looking for from the group or Steve, where your article said: “One consequence could be that content on hover or focus should be triggered via scripts rather than via CSS pseudo-classes to prevent a situation where the content pops up again straight after dismissal.” I think that is a fairly straightforward: If you use only CSS to create content on hover (or focus), then it must be for input errors or not replace other content. You could theoretically create a keyboard event that hides any content shown on hover, but it would be very difficult to do in a reasonable way. Given the difficulty they can cause, the idea was that people would avoid this or put the necessary work in to do it well (which includes JS). -Alastair
Received on Tuesday, 28 August 2018 14:30:36 UTC