W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)

From: James Craig <jcraig@apple.com>
Date: Fri, 21 Sep 2012 16:54:56 -0700
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, w3c-wai-pf@w3.org
Message-id: <7059D884-69CD-4CB5-89D7-5B2BAFA33C8B@apple.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>

On Sep 19, 2012, at 2:37 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote:

> James Craig, Wed, 19 Sep 2012 13:52:57 -0700:
>> On Sep 15, 2012, at 8:22 AM, Laura Carlson wrote:
>>>> To the best of my knowledge, one of these approaches (the iframe
>>>> example listed at http://cookiecrook.com/longdesc/iframe/)
>>> iframe to the best of my knowledge:
>>> http://www.d.umn.edu/~lcarlson/research/constriants/iframe.html
>> I disagree with all of those conclusions, and must also note that 
>> your synopsis fails to mention that longdesc is not implemented in 
>> many major browsers, while iframe is implemented in all of them.
> It is often appreciated (for example the chairs when they evaluate 
> polls), if one admits the drawbacks. It would be interesting to know if 
> you are able to point out *any* negative effects of using <iframe>.

The only one that comes to mind is that there is no way in HTML to semantically relate the <img> and <iframe>. 
That said, you could probably use aria-flowto to represent that relationship. 

Received on Friday, 21 September 2012 23:55:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:31 UTC