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

(unknown charset) Re: CP, ISSUE-30: Link longdesc to role of img [Was: hypothetical question on longdesc]

From: (unknown charset) Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Tue, 20 Mar 2012 14:32:47 +0100
To: (unknown charset) Sam Ruby <rubys@intertwingly.net>
Cc: (unknown charset) Laura Carlson <laura.lee.carlson@gmail.com>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, public-html@w3.org
Message-ID: <20120320143247432278.1dbc9777@xn--mlform-iua.no>
Sam Ruby, Tue, 20 Mar 2012 06:25:36 -0400:
> On 03/20/2012 02:43 AM, Leif Halvard Silli wrote:

> First: is there any way that the people who are working on these 
> proposals (in this case this includes, but is no limited to: Laura 
> and Leif) can work together to converge on a single proposal?

I will co-operate in the following way: If Laura/the A11Y TF don't 
support it or suggests integrating [bits of] it in the other CP, then 
I'll withdraw it.
 
> Second: what we will need in order to proceed here is use cases that 
> directly and specifically require the addition(s) described in the 
> Change Proposal.

Given that e.g. AT will see e.g. an <object data=img role=img> as 
virtually no different from an <img> element, aren't those use cases 
covered already? The only thing 'extra' is the question about why to 
use e.g <object data=img role=img> instead of <img src=img> in the 
first place. But those reasons - of which I could think of a few - such 
as flash images  and fallback from object to img element etc. But these 
reasons are not, it seems to me, linked to ISSUE-30.

>  Testimonial that some are willing to implemented it 
> (both authors and implementors) would also help your case.

I don't know how much buy-in from implementers would be possible for 
longdesc on object, embed and canvas. I think we already have a level 
of implementation of <iframe @longdesc>. Would it be sufficient with 
use cases? Or must UA/AT support demonstrated to? 

> Failing 
> that, I suspect that the answer would be that at this time, this is 
> best addressed either in an extension spec or in a subsequent release 
> of HTML.
> 
> Compare the use cases that were linked to by the original longdesc 
> change proposal:
> 
http://www.w3.org/html/wg/wiki/index.php?title=LongdescRetention&oldid=7512#Use_Cases
> 
> Against the ones that were provided by the revised proposal:
> 
> http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc/UseCases

Again, I only cover img, iframe, object, canvas with role=img. To me 
the usecases thus seems the same. What is not the same, is related to 
the preference of one element over another. Do you want documentation 
for that?
-- 
leif h silli
Received on Tuesday, 20 March 2012 13:33:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:47 GMT