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: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 19 Sep 2012 23:33:22 +0200
To: James Craig <jcraig@apple.com>
Cc: Charles McCathie Nevile <chaals@yandex-team.ru>, HTML Accessibility Task Force <public-html-a11y@w3.org>, w3c-wai-pf@w3.org
Message-ID: <20120919233322003192.2f7c0a05@xn--mlform-iua.no>
James Craig, Wed, 19 Sep 2012 12:56:13 -0700:
> On Sep 15, 2012, at 7:53 AM, Charles McCathie Nevile 

>> (For completeness in your alternatives, you should list the idea of 
>> longdesc pointing to a link on the page and doing the magic to 
>> follow that. I suggest that such a technique needs to include a 
>> discussion of maintaining content which relies on that pattern, 
>> which is where the major difficulties arise).
> I will add it. I assume you mean something like this? 
> <img src="…" longdesc="#link"><a id="link" href="data.html">Foo</a>
> FWIW, I think that's probably a better implementation idea than the 
> current proposal for "DescribedAt":
> <img src="…" aria-describedat="#link"><a id="link" href="data.html">Foo</a>
> rel="longdesc" or no?

If you really want to be complete, then HTML5 already mentions using 
@usemap (image maps).
leif halvard silli
Received on Wednesday, 19 September 2012 21:33:57 UTC

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