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

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

From: David Singer <singer@apple.com>
Date: Wed, 21 Mar 2012 15:23:50 -0700
Cc: "janina@rednote.net" <janina@rednote.net>, John Foliot <john@foliot.ca>, 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, "'xn--mlform-iua@målform.no'" <xn--mlform-iua@xn--mlform-iua.no>, "rubys@intertwingly.net" <rubys@intertwingly.net>, "laura.lee.carlson@gmail.com" <laura.lee.carlson@gmail.com>, "mjs@apple.com" <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, "public-html@w3.org" <public-html@w3.org>
Message-id: <D1C8C526-DAD3-484C-9958-4C2889720663@apple.com>
To: Sean Hayes <Sean.Hayes@microsoft.com>

On Mar 21, 2012, at 15:08 , Sean Hayes wrote:
> In order to satisfy the use case though, I don't think it really matters if both parts are co-located in a single resource at the end of a single longdesc link, or in two resources at the end of two distinct links. What I do think matters however is that when the image description is not semantically a subset of the video description, there is a clear dividing line so that the browser (or AT) can provide the right amount of information to the user. Two clearly labeled links naturally provides that division, a single link does not, and therefore implies a mechanism would need to be in place in the resource pointed to. I'm happy either way provided the use case is met.
> 

I think if we had the clear designs for providing the description of the video, we could easily decide; worse, that much of the current discussion takes so much time because we don't have a clear solution to the larger problem, and so a solution to the smaller has no foundation.

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 21 March 2012 22:25:07 GMT

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