E-mail List Archives
Re: accessible tree menus
From: Jim Thatcher
Date: Feb 28, 2009 10:35AM
- Next message: John Foliot: "Re: accessible tree menus"
- Previous message: Chris Hoffman: "Re: accessible tree menus"
- Next message in Thread: John Foliot: "Re: accessible tree menus"
- Previous message in Thread: Chris Hoffman: "Re: accessible tree menus"
- View all messages in this Thread
Well Chris, it is hard for me to imagine a link working, but
http://Bookshare.org that I mentioned in the last post uses arrow keys for
keyboard users, just like a Windows menu system, and headings (h3)
navigation for screen reader users since, for them, arrows are "in use"
(until ARIA is well supported).
Accessibility Consulting: http://jimthatcher.com/
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Chris Hoffman
Sent: Saturday, February 28, 2009 10:52 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] accessible tree menus
On Fri, Feb 27, 2009 at 2:47 PM, John Foliot < <EMAIL REMOVED> > wrote:
> *IF* you think that 36 links visually hidden but none-the-less present in
> the source code represents an accessible solution, sure. (I don't)
> Thing is, those links are "compacted" to avoid visual clutter, but for
> non-seeing users, they still need to put up with the audio clutter.
Would having some sort of mechanism (oh, say, a _link_) that allows
users to easily skip from one menu to another without having to read
through every menu item help in this situation?