- From: Charles McCathieNevile <charles@w3.org>
- Date: Sun, 9 Dec 2001 10:18:31 -0500 (EST)
- To: David Woolley <david@djwhome.demon.co.uk>
- cc: <w3c-wai-ig@w3.org>, <cturne@essex.ac.uk>
Yes, what happens for a mouse user is that they click on the box (equivalent in explorer to alt-down arrow) and then scroll up und down the list until they have selected the item tehy want, at which point they release. Usually there is no visual difference - the following button is often provided, but a javascript frees the user from having to click it. I think that the problem is not with HTML, but with browsers that force an onChange event to be fired when you try to select with the arrow keys, instead of waiting for you to move out of the combobox before registering whether you have changed the selected item. I don't know how many browsers have this problem, although I have noted it is a common experience for users of Jaws with IE. cheers Charles McCN On Sun, 9 Dec 2001, David Woolley wrote: > > kind of comboboxes which only activate when you press some button > after > > them, as opposed to the ones which activate as soon as you press > cursor > > down. I mean what would a mouse-user do with these different kinds of This sounds like a case of Document Object Model (popularly called JavaScript) onchange events being used. The change wouldn't be recognized until the mouse button was released. It's not an HTML problem, but a designer problem (designing only for clicking with a mouse). Plain HTML will not do this. -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Sunday, 9 December 2001 10:18:34 UTC