Comments on: Too much accessibility – multiple JavaScript event handlers http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/ Mon, 13 Oct 2008 04:58:01 +0000 http://wordpress.org/?v=2.5 By: Bim http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-30089 Bim Tue, 31 Jul 2007 07:38:48 +0000 http://www.rnib.org.uk/wacblog/general/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-30089 The site I referred to also used both onClick and onKeyPress for its top level links. The same thing happened, trying to tab across them activated the first link with both event handlers. This only happened in Firefox. Are you saying that the browser handled it incorrectly? The site I referred to also used both onClick and onKeyPress for its top level links. The same thing happened, trying to tab across them activated the first link with both event handlers. This only happened in Firefox. Are you saying that the browser handled it incorrectly?

]]> By: Martin Kliehm http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-30013 Martin Kliehm Mon, 30 Jul 2007 14:28:06 +0000 http://www.rnib.org.uk/wacblog/general/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-30013 You mean there was a simple inline onkeypress attribute bound to the search form? OK, that's not so smart. But I can't see any evil if the keypress event is bound to an element and checked which key has been pressed. Only if it's the enter key (keycode 13) on a link or a button, or the space bar (keycode 32) on a checkbox or radio button, the intended function should be evoked. You mean there was a simple inline onkeypress attribute bound to the search form? OK, that’s not so smart. But I can’t see any evil if the keypress event is bound to an element and checked which key has been pressed. Only if it’s the enter key (keycode 13) on a link or a button, or the space bar (keycode 32) on a checkbox or radio button, the intended function should be evoked.

]]> By: JackP http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-5430 JackP Mon, 20 Nov 2006 13:04:52 +0000 http://www.rnib.org.uk/wacblog/general/too-much-accessibility-%e2%80%93-multiple-javascript-event-handlers/#comment-5430 Talking of javascript - it's offtopic slightly so I apologise and feel free to delete if you don't feel it's relevant - I produced a testcase for the use of the javascript postback in .NET (http://www.thepickards.co.uk/index.php/200610/javascript-testcase/) as under WCAG 1.0 you can't rely on javascript, and I was simply seeking to determine whether or not the "postback" part of javascript is sufficiently supported by screenreaders and other AT as to be deemed "accessible", even though it would obviously fail WCAG 1.0 if you relied on it. The feedback I've had so far would seem to suggest that it does work as expected, but I thought there might be someone there who has sufficient screen reader experience to offer another opinion or further advice? Talking of javascript - it’s offtopic slightly so I apologise and feel free to delete if you don’t feel it’s relevant - I produced a testcase for the use of the javascript postback in .NET (http://www.thepickards.co.uk/index.php/200610/javascript-testcase/) as under WCAG 1.0 you can’t rely on javascript, and I was simply seeking to determine whether or not the “postback” part of javascript is sufficiently supported by screenreaders and other AT as to be deemed “accessible”, even though it would obviously fail WCAG 1.0 if you relied on it.

The feedback I’ve had so far would seem to suggest that it does work as expected, but I thought there might be someone there who has sufficient screen reader experience to offer another opinion or further advice?

]]>