I've been playing with making drop down menus work with both mouse and keyboard navigation. Basically take the default css (suckerfish) style drop down and add unique id's for each ul tag and add an onfocus for each <a href tag that calls about nine lines of js to allow keyboard navigation.
So whats the problem?
Well now I've got a menu that fully works and is accsessable by both mouse & keyboard as long as js is enabled.
If js is disabled the dropdown with mouse still works but the keyboard doesn't activate the dropdown, which is always the case with suckerfish style menus. At least the status bar shows the URL.
So what's the question? Should I feel good or bad that I've made something more accessable by using the devils js? Have i gone forward or backward in terms of accessibility?
There are several ways to give focus to an element:
* Designate the element with a pointing device. * Navigate from one element to the next with the keyboard. The document's author may define a tabbing order that specifies the order in which elements will receive focus if the user navigates the document with the keyboard (see tabbing navigation). Once selected, an element may be activated by some other key sequence. * Select an element through an access key (sometimes called "keyboard shortcut" or "keyboard accelerator").
[edited by: pageoneresults at 12:40 pm (utc) on June 25, 2007] [edit reason] Trimmed Quote - Please Refer to TOS [/edit]