- From: Charles McCathieNevile <charles@w3.org>
- Date: Fri, 7 Apr 2000 11:09:49 -0400 (EDT)
- To: Bruce Bailey <bbailey@clark.net>
- cc: Accessibility Listserve <w3c-wai-ig@w3.org>, Jeffrey pledger <jpledger@mindspring.com>, smccaffr@MAIL.NYSED.GOV
Adding onfocus is the right approach for HTML4. Replacing them in the language itself is the approach for the future (whch will take some time to show up...) keypresses should be added where you look for mouseclicks, and the future approach is to have an activate event which can be triggered from any device. Charles McCN On Fri, 7 Apr 2000, Bruce Bailey wrote: If they got it right, and (in any case) as a matter of actual practice, this means that onFocus must be ADDED to tags that use onMouseOver and CANNOT merely REPLACE that element. (So we are pushed away from device-independent tags). Do any of the more widely supported keyboard-oriented tags (onKeyPress, onKeyDown, onKeyUp) simulate the onFocus/onBlur? If I am going to have to use two tags to do the same thing, I might as well use ones that validate! Thanks very much. > Right. Hence the use of focus. > There has been more extensive discussion of event triggers and > accessibility > in the User Agent group, and others. > > On Fri, 7 Apr 2000, Bruce Bailey wrote: >> Take the case of user with good vision but poor motor skills. He would >> quite likely navigate the a page with the tab key. When he has the >> image/link under discussion selected, should it not trigger the visual >> effect (via onFocus)? onMouseOver doesn't cut it for this >> case! I don't think onKeyPress does it either. -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Friday, 7 April 2000 11:09:52 UTC