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

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

From: Leif H Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Sat, 23 Apr 2011 17:59:59 +0200
To: jonas@sicking.cc
Cc: jonas@sicking.cc, faulkner.steve@gmail.com, cooper@w3.org, clown@alum.mit.edu, wai-xtech@w3.org, public-html@w3.org, schwer@us.ibm.com, dbolter@mozilla.com, mjs@apple.com
Message-ID: <0087329796.988048799@xn--mlform-iua.no>
Reply to Jonas:
>>>In fact, we could even display a context menu item
>>>for each link if there are multiple as aria-describedby allows
>>>pointing to multiple elements, many of which could be links.
>>
>>Then some would use @aria-describedby for the purpose of the link,
>>while others would use it for the purpose of its text content = purpose
>>crash.
>
>That is your interpretation of the ARIA spec. One that I don't agree
>with. And based on the subject of this thread, one that the spec
>editors might not agree with either.
>
>My interpretation is that everyone should see the link.

Like Maciej allready replied, it is important what you mean by "see". 
Except VoiceOver users and other keyboard users, everyone see longdesk if 
they use iCab. That many don't see longdesk is a problem due to the user 
agents.

When it comes to the interpretation of ARIA: Steve documented that AT 
SHOULD present content pointed out by aria-describedby as markup.

So do you want to make the presentation of description links depend on that 
the SHOULD becomes a MUST?

It seems to me that the longdesklink should be available to AT even without 
such a MUST.
--
leif h silli 
Received on Saturday, 23 April 2011 16:01:53 UTC

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