W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: False aria-describedby expectations in ARIA Authoring Practices (longdesc)

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 26 Apr 2011 13:48:20 -0700
Message-ID: <BANLkTik-QR9vMbCjdXsk_WsjENbqQYDeEg@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: Joseph Scheuhammer <clown@alum.mit.edu>, Michael Cooper <cooper@w3.org>, David Bolter <dbolter@mozilla.com>, Steve Faulkner <faulkner.steve@gmail.com>, HTMLwg <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>, wai-xtech-request@w3.org, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
On Tue, Apr 26, 2011 at 1:41 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> On Tue, Apr 26, 2011 at 6:48 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
> wrote:
>>
>> Hi Jonas,
>>
>> ARIA is going through Candidate Recommendation so changing the browser
>> implementation this late in the game is problematic. I read through the code
>> and I don't see what the patch does for accessibility. It appears to simply
>> be iterating through valid ids that match the describedby reference. What
>> are you actually doing with this patch as it is not clear?
>
> Huh? I don't understand why the spec status affects the ability to fix bugs
> in the various implementations? Going to rec freezes the spec, not the
> implementations.

Sorry, forgot to answer the questions regarding what the patch does.

We already have code to expose longdesc to AT software. What the patch
does is that it detects that if an image doesn't have a longdesc
attribute, but does have a aria-describedby which points to a <a> or
<area> element with a href attribute, it exposes the link in that
<a>/<area> as being the location of the long description of the image.

/ Jonas
Received on Tuesday, 26 April 2011 20:49:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:24 UTC