- From: Charles McCathieNevile <charles@w3.org>
- Date: Fri, 5 Mar 1999 13:45:21 -0500 (EST)
- To: Kelly Ford <kford@teleport.com>
- cc: Chris Kreussling <CHRIS.KREUSSLING@ny.frb.org>, WAI <w3c-wai-ig@w3.org>, WAI UA group <w3c-wai-ua@w3.org>
This is a User Agent implementation issue. In this case I would say that the implementation of keyboard access is not intuitive. Which means that the documentation of alt-down-arrow is crucial for accessibility. Charles On Fri, 5 Mar 1999, Kelly Ford wrote: At 12:55 PM 3/5/99 -0500, Chris Kreussling wrote: > >As far as I know, there's no way to *navigate* through a selection list by keyboard without also selecting each option of the list in turn. Simply moving through the list "selects" the option, which triggers the onChange event. The only way to avoid "selecting" a state is to *scroll* through the list by clicking the drop-down button, clicking the scroll bar to find the state you want, then clicking the state. Notice the "click, click, click" here. There's no way to do this action by keyboard alone, so this is an accessibility design issue. Try pressing alt-down arrow when on the list. I did this on the page and could move through the list of states without triggering the event. If I pressed enter on the state I wanted, again after pressing alt-down arrow and moving through the list, I then went to my selected state. --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://purl.oclc.org/net/charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Friday, 5 March 1999 13:45:42 UTC