Re: Drop longdesc, get aria-describedat?

On Fri, Mar 9, 2012 at 4:14 AM, Silvia Pfeiffer
<> wrote:
> On Fri, Mar 9, 2012 at 12:49 PM, Leif Halvard Silli
> <> wrote:
>> Laura Carlson, Thu, 8 Mar 2012 12:06:52 -0600:
>> First off: Steve yesterday confirmed that Internet Explorer's longdesc
>> implementation is plain wrong: It treats the URL as text string. Thus
>> it implements it precisely the way the WHATWG blog once ridiculed the
>> @longdesc usage for.  See this bug:
> If that is indeed the case, then all those people that have put
> hyperlinks into the @longdesc attribute have ended up with non-usable
> longdesc values in IE. @longdesc is therefore not usable for the
> purposes that we intend it to be used for, since it is not implemented
> compatibly across browsers.

(a) That @longdesc is not reliably implemented across all popular user
agents is hardly news.

(b) Even if @longdesc is exposed as a string in some MSAA field in
some versions of IE, that does not mean that behavior is not expected
and handled by key AT such as JAWS, Window-Eyes, and Dolphin. For
example, they may just query the DOM directly in IE's case.
Notoriously, a lot of accessibility has to be hacked on top of MSAA
because its semantics are woefully inadequate.

> This to me is a very strong argument to move on to a new attribute so
> we can start on a clean slate for all relevant elements with well
> defined implementation details.

You'll stil have to hack on top of MSAA somehow.

Benjamin Hawkes-Lewis

Received on Friday, 9 March 2012 06:16:33 UTC