Why do you do the aria-labelledby pointing into the span?
Otherwise the accessible name for the top level items encompasses all the
subitems too, right?
I didn't realize that we need to do that. I'm not sure if this is a better
way anymore -- it's confusing for authors to have to do that.
Sigh :/
- Aaron
From:
James Craig <jcraig@apple.com>
To:
Aaron M Leventhal/Cambridge/IBM@IBMUS
Cc:
Jon Gunderson <jongund@illinois.edu>, Cynthia Shelly
<cyns@exchange.microsoft.com>, George Young <gcyoung@microsoft.com>, W3C
WAI-XTECH <wai-xtech@w3.org>
Date:
09/08/2008 08:24 PM
Subject:
Re: Tree sample code
Aaron M Leventhal wrote:
Cynthia, what do you think about having your tree widget have the keyboard
UI of a tree?
I think the one I created serves that request, doesn't it? If it's missing
something, please advise.
http://cookiecrook.com/test/aria/tree/ariatree.html
You could still have it gracefully degrade into nested lists of links in
screen reader virtual buffers.
That's a good recommendation to make, but I don't think it's necessary to
do that amount of browser checking and rewriting for the example code, do
you? One caveat though. Instead of maintaining a list of user agents that
support ARIA, maintain a list of old user agents that are known to not
support ARIA. Assume the best of unknown user agent strings, and serve up
the full ARIA support.
James