- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 17 Oct 2017 23:36:57 +0100
- To: w3c-wai-gl@w3.org
On 17/10/2017 18:14, Repsher, Stephen J wrote: > I’m looking for some conformational feedback on a simple question: If > content appears only on hover, i.e. the trigger is not focusable, does > that *always* constitute a WCAG 2.0 failure? In the context of 2.1.1, I > suppose this asks whether the ability to show the content is considered > “functionality” and thus must be keyboard operable. One example might > be where a help icon is used to show extra info for a form field and is > piped to the accessible description: > > <label>Reason<input type=”text” … > aria-describedby=”tooltip”></label><img src=”help-icon.png” … > onmouseover=”showTooltip()”> > > Depending on your answer above… > > If you answered yes, then doesn’t that translate to saying that any > element with a title attribute must be focusable, either by default from > its semantics or manually via setting its tab index? For example: > > <img … alt=”blah” title=”more blah” tabindex=”0”> Yes, and yes. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 17 October 2017 22:37:21 UTC