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

Re: longdesc (was Re: use of aria-hidden to provide a text description not visible on the page.)

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Wed, 15 Sep 2010 07:50:36 +0100
Message-ID: <AANLkTimptXLTj5kg=5yKXzn1BpotAQy5ww_NjXECTkZ4@mail.gmail.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: W3C WAI-XTECH <wai-xtech@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
hi Laura,

>This technique along with many other that have surfaced recently seem
>to be a reaction to longdesc being dropped from HTML5.

since i started this thread I am clear on what it was a reaction to, and I
can state unequivocally it was not motivated by anything to do with trying
to find a replacement for longdesc. It is/was an attempt understand how
aria-labelledby and aria-describedby should treat referenced hidden content.
Something to remember: although the example uses an image aria-labelledby
and aria-describedby can be used on ANY element.


regards
Stevef

On 14 September 2010 21:56, Laura Carlson <laura.lee.carlson@gmail.com>wrote:

> David Bolter  wrote:
> >   Sorry a bit rushed here and I don't feel like I fully understand this
> > thread.
>
> This technique along with many other that have surfaced recently seem
> to be a reaction to longdesc being dropped from HTML5.
>
> No one has come up with anything simpler or better than longdesc.
> Banishing an existing solution while not providing a better solution,
> it not a solution. All solutions presented to date seem to me to be
> convoluted hacks. The existing solution should have been improved (we
> had bugs on how to do that [1] [2] [3] [4]), or the existing solution
> should be gracefully replaced with a better solution.
>
> The Chairs' Decision [5] states that:
>
> QUOTE
>
> This issue can be reopened if new information comes up. Examples of
> possible relevant new information include:
>
> * use cases that specifically require longdesc,
> * evidence that correct usage is growing rapidly and that that growth
> is expected to continue, or
> * widespread interoperable implementation.
>
> UNQUOTE
>
> I have been researching and amassing use cases of Longdesc in the Wild.
> http://www.d.umn.edu/~lcarlson/research/ld.html
>
> Is this information grounds to reopen the issue or the basis for a
> formal objection?
>
> Best Regards,
> Laura
>
> [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10019
> [2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10017
> [3] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10018
> [4] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10015
> [5]
> http://lists.w3.org/Archives/Public/public-html/2010Aug/att-0112/issue-30-decision.html
>
> --
> Laura L. Carlson
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 15 September 2010 06:51:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:44 UTC