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: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 20 Mar 2012 08:58:24 -0500
Message-ID: <CAOavpvfGeuB=de8-6Hb+JjjZi2N9Cmb62q=oZE2Ho0MW9DA0yA@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, public-html@w3.org, Judy Brewer <jbrewer@w3.org>, Janina Sajka <janina@rednote.net>
Hi Leif,

Thanks for your hard work on this.

Due to the HTML Chairs delay on ISSUE-30 I have asked Sam, Paul and
Maciej to open a new Issue (ISSUE-206) for expanding longdesc to other
elements after ISSUE-30 is decided:

http://lists.w3.org/Archives/Public/public-html-a11y/2012Mar/0209.html
http://lists.w3.org/Archives/Public/public-html-a11y/2012Mar/0210.html
http://lists.w3.org/Archives/Public/public-html-a11y/2012Mar/0212.html

I await their reply of whether they will open an ISSUE-206 (if
ISSUE-30 results in including longdesc in the spec). Hopefully they
will decide this in a timely manner.

Janina, this would be the two step process that you spoke of last week.

Best Regards,
Laura

On Tue, Mar 20, 2012 at 1:43 AM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Chairs, Laura and all,
>
> Please accept this change proposal to allow @longdesc on any *embedded*
> element in the HTML namespace which has the  implied or specified 'img'
> role:
>
> http://www.w3.org/html/wg/wiki/ChangeProposals/LinkLongdescToRoleOfImg
>
> The main idea of the CP:
>
> * To allow @longdesc on any *embedded* HTML namespace element of
>  role 'img': img, iframe, canvas, embed, object.
> * To say that @longdesc should only be used for describing images,
>  and thus not for describing e.g. tables - tables can be a task
>  for ARIA-describedAT, and I justify why in the CP.
> * The limitation to embedded content is because, on such elements,
>  contextual menus - which is how longdesc is typically presented,
>  have pretty good discoverability in non-AT user agents: Users
>  tend to use context menus on such elements. Compared to on
>  'normal' elements, which usually do not have context menus,
>  except a general context menu for to the entire page.
>
> For the video element, then I am open to consider the idea of that
> @longdesc could point to a poster description: It makes some sense, as
> the poster is an image. But I have so far not included that in the CP.
> --
> Leif Halvard Silli



-- 
Laura L. Carlson
Received on Tuesday, 20 March 2012 13:59:00 GMT

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