- From: Repsher, Stephen J <stephen.j.repsher@boeing.com>
- Date: Tue, 17 Oct 2017 17:14:58 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <0b7112f8882e4e4581701380fa50c54d@XCH15-08-08.nw.nos.boeing.com>
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"> If you answered no, then can you offer examples and explain why they are fully accessible (I don't think mine above actually is)? Steve Repsher Twitter<https://twitter.com/steverep> | LinkedIn<https://www.linkedin.com/in/steverepsherjr/> | GitHub<https://github.com/steverep>
Received on Tuesday, 17 October 2017 17:15:28 UTC