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

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

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Thu, 2 Jun 2011 23:11:28 +0200
To: Jonas Sicking <jonas@sicking.cc>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Sam Ruby <rubys@intertwingly.net>, HTML WG LIST <public-html@w3.org>
Message-ID: <20110602231128994579.3780396f@xn--mlform-iua.no>
Jonas Sicking, Thu, 2 Jun 2011 08:21:32 -0700:
> On Wed, Jun 1, 2011 at 4:18 PM, Silvia Pfeiffer wrote:

>> 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.

> 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.

REQUIRED is a synonym for MUST. ARIA 1.0 itself seems silent on this 
matter. Whereas the normative 'WAI-ARIA 1.0 User Agent Implementation 
Guide' offers a clear SHOULD: [1]

]] Note that aria-describedby may reference structured or interactive 
information where users would want to be able to navigate to different 
sections of content. User agents MAY provide a way for the user to 
navigate to structured information referenced by aria-describedby and 
assistive technology SHOULD provide such a method. [[

In any case, my impression from what you have said earlier, is that you 
are working on a CP which describe how to use aria-describedby to 
exposee links. And nothing more.

[1] http://www.w3.org/TR/wai-aria-implementation
-- 
Leif Halvard Silli
Received on Thursday, 2 June 2011 21:12:00 UTC

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