Think of onclick as a 2-action process: mouse down selects the object, mouse up - if still on-focus - activates the link, in this instance. Same for keyboard action: tab to object selects it, enter/return activates it.
Oh, something just occurred to me: best make it explicit that we're talking about onclick behaviours on elements that receive focus via the keyboard (links, form elements). obviously, if you have applied onclick to something else (like a plain vanilla image, or a paragraph, etc), it won't be triggered by the keyboard because the user will not be able to even get to it. but that then becomes a more fundamental accessibility issue.
Tell you what, why not run a sequence of tests? Proof of pudding ...I can knock something together this saturday and test in most recent-ish (from IE 4 onwards) browsers, if you like. Anybody who can test on Mac (ideally both OS 9 and OS X) and *nix (konqueror)? Send me a reply off list...I'll collate the results and re-post them here.
Patrick -- _____________________________________________________ re�dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
