- From: Charles McCathieNevile <chaals@opera.com>
- Date: Tue, 13 Mar 2012 08:08:46 +0100
- To: "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>, "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>
- Cc: "John Foliot" <john@foliot.ca>, RichardSchwerdtfeger <schwer@us.ibm.com>, "W3C WAI-XTECH" <wai-xtech@w3.org>, "HTMLAccessibility Task Force" <public-html-a11y@w3.org>
On Tue, 13 Mar 2012 06:40:48 +0100, Leif Halvard Silli
<xn--mlform-iua@målform.no> wrote:
> One thing that struck me, as I was writing this - at least the things
> relating to fallback, is that much of what I was describing probably
> only makes sense for the <img> element. Simply because only the <img>
> element has a such a specific behavior whenever it isn't displayed.
Longdesc isn't default fallback, it is extended support. (Or some such
terminology).
> E.g. for <video>, <audio> etc, then there is no guaranteed fallback.
> And even if there is fallback, it isn't guaranteed to be a textual
> substitute.
There's no guarantee that the long explanation of an image is textual,
either. (Somewhere there is an example I made with audio, to illustrate a
different idea, or think of multi-modal CAPTCHA).
> This, IMO, points towards 'the HTML feature' rather than
> 'an ARIA feature'.
Right.
cheers
--
Charles 'chaals' McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg kan litt norsk
http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Tuesday, 13 March 2012 07:09:40 UTC