- From: Charles Pritchard <chuck@jumis.com>
- Date: Wed, 21 Mar 2012 00:55:12 -0700
- To: John Foliot <john@foliot.ca>
- CC: 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, 'David Singer' <singer@apple.com>, janina@rednote.net, "'xn--mlform-iua@målform.no'" <xn--mlform-iua@xn--mlform-iua.no>, rubys@intertwingly.net, laura.lee.carlson@gmail.com, mjs@apple.com, paul.cotton@microsoft.com, public-html-a11y@w3.org, public-html@w3.org
On 3/20/2012 11:18 PM, John Foliot wrote: > This is the very same reason why aria-describedby cannot point to "hidden" > text, as it too will be flattened to the same string text, using the same > computational rules. Can we get by with aria-describedby pointing to an embedded image tag? <video poster="poster.jpg" aria-describedby="poster" longdesc="videolongdesc.html" aria-label="My video"> <a href="videolongdesc.html" title="My Video"><img id="poster" src="poster.jpg" longdesc="posterlongdesc.html" alt="My Poster" /></a> </video> We're pointing aria-describedby at an element with special semantics: img @longdesc, and it's not a display: none/@hidden element, so we're not violating any laws there... though I would have no expectation that the img could gain focus as fallback for video. It looks kind of ok from an ARIA perspective, though it still loses a little something from non-aria. I've argued we may want to look at allowing users/authors more easy access to displaying fallback content. In that case, the typical user could both see the longdesc, and see the fallback content (and then follow that longdesc). -Charles
Received on Wednesday, 21 March 2012 07:55:41 UTC