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

Re: Longdesc extension specification

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Tue, 25 Sep 2012 14:50:05 +0200
To: Sam Ruby <rubys@intertwingly.net>
Cc: Charles McCathie Nevile <chaals@yandex-team.ru>, public-html-a11y@w3.org, Michael(tm) Smith (mike@w3.org) <mike@w3.org>
Message-ID: <20120925145005292616.6dfc18cf@xn--mlform-iua.no>
Sam Ruby, Tue, 25 Sep 2012 08:08:58 -0400:
> On 09/25/2012 08:02 AM, Leif Halvard Silli wrote:
>> Sam Ruby, Mon, 24 Sep 2012 09:39:46 -0400:
>>> On 09/24/2012 09:28 AM, Charles McCathie Nevile wrote:
>>> Work with Mike Smith to get access to CVS and/or to create a bugzilla
>>> component when you are ready.
>> I'll wait with spec feedback till the bugzilla is ready.
> Before creating a component, some discussion on the title for this 
> document[1] may be in order.
> Is the intent to add long descriptions to other elements be handled 
> by separate extension specifications?
> - Sam Ruby
> [1] 

Good question. You pointed out that the spec should describe 'today'. 
From that angle, it seems logical to focus on only images. Though, from 
a 'today' perspective, one could also include iframe, which per HTML4 
can take longdesc. I don't remember if support for longdesc on iframe 
is widely implemented, but I seem o remember that I test it, and found 
it not to be widely implemented - which could be a reason to not 
include iframe, from a 'today' perspective.  Be that as it may. Curren 
title is 'HTML5 image description links'.

My current proposal:

	"The HTML5 longdesc attribute.
     A description link for A11Y APIs and other implementations."

The title does not include 'img' or 'image' - to keep the options open. 
At the same time the title avoids hinting anything about other methods 
for linking.
leif h silli
Received on Tuesday, 25 September 2012 12:53:44 UTC

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