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

Re: Drop longdesc, get aria-describedat?

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 14 Mar 2012 17:41:12 +0100
To: Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: John Foliot <john@foliot.ca>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Charles McCathieNevile <chaals@opera.com>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLAccessibility Task Force <public-html-a11y@w3.org>
Message-ID: <20120314174112766233.f2fba1cb@xn--mlform-iua.no>
Richard Schwerdtfeger, Wed, 14 Mar 2012 10:39:01 -0500:
> First formal longdesc mappings to accessibility API was never done by 
> industry. Consequently implementations vary.
  [ snip ]
> Steve and I are working on an ARIA 
> placement for longdesc that we intent to be better specified to meet 
> the use case. 

+1 This is highly appreciated. Hopefully in ARIA 1.0?

I propose that ARIA directs ATs to make use of @longdesc in the 
following situations [of course on the condition that the host language 
allows longdesc in these situations]:
 
 * On any element of role 'img'.
 * On any element of role 'application' or 'document', which are the
   roles that HTML5 permits for <iframe>. Role 'application' is also
   the only role that HTML5 permits for <video> and <audio>.
 * On any other element that the host language permits it on, such as
   <iframe> and <img> without any role in HTML4 and [knocking on wood]
   in HTML5, unless the host element is declared to be presentational
   or with another role that is not compatible with the implied 
   semantics of a 'description link'.
-- 
Leif Halvard Silli
Received on Wednesday, 14 March 2012 16:41:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:56:05 UTC