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

Re: ISSUE-30 longdesc - Chairs Solicit Alternate Proposals or Counter-Proposals

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 02 Jun 2011 09:18:48 -0700
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Sam Ruby <rubys@intertwingly.net>, HTML WG LIST <public-html@w3.org>
Message-id: <B36948AF-1DBE-4FE9-A4E9-7C9CAF64829E@apple.com>
To: Jonas Sicking <jonas@sicking.cc>

On Jun 2, 2011, at 8:21 AM, Jonas Sicking wrote:

> On Wed, Jun 1, 2011 at 4:18 PM, Silvia Pfeiffer
> <silviapfeiffer1@gmail.com> wrote:
>> I am told that right now browsers turn the html snippet that
>> aria-describedby points to into plain text before giving it to
>> accessibiltiy APIs and thus screen readers cannot e.g. change their
>> accent to a different content language, or point out that there's a
>> url to another resource.
>> 
>> Thus, I suggest your change proposal should also include that browsers
>> need to expose the markup of the html snippet(s) that aria-describedby
>> points to to accessibility APIs.
> 
> That conflicts with the information I'm getting from the Firefox
> accessibility team. At least for non-hidden content Firefox should be
> fully exposed including all its html semantics to AT users.
> 
> In any case, ARIA is already requiring what you're asking for. This is
> why I was suggesting that the HTML spec simply points this fact out
> while referring to the ARIA spec.

I'm not sure if WebKit (or Safari in particular) exposes full semantics of aria-describedby content, but I tentatively think it is a reasonable requirement, whether stated in ARIA or in HTML or both.

Regards,
Maciej
Received on Thursday, 2 June 2011 16:19:20 GMT

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