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.
They do the same job, across all browsers. Tell you what, why not run a sequence of tests? Proof of pudding ... Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Harwood Sent: 26 November 2004 22:28 To: [EMAIL PROTECTED] Subject: RE: [WSG] IE's New JavaScript Blocking Feature On Fri, 26 Nov 2004 16:05 , Derek Featherstone <[EMAIL PROTECTED]> sent: >My vote: let the automated checkers moan about this all day. Ignore them. >Don't add onkeypress in the name of accessibility and device independence... Try telling that to SOCTiM who check all local council sites, they take the guidlines as if there written in stone! ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.2 - Release Date: 24/11/04 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.2 - Release Date: 24/11/04 ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
