Comments on: JavaScript Keyboard Accessibility

By: Grey

Grey — Sat, 14 Apr 2007 22:16:06 +0000

@Kevin: OK, thanks for pointers. I was confused by your use of “#” or “javascript:;”. If you add the link, you don’t need to have a href attribute, as far as I know…

By: David Hucklesby

David Hucklesby — Thu, 12 Apr 2007 19:17:38 +0000

may be problematical, as some browsers take this as a link to the top of the page.

I suggest - with no real fragment ID of “void”.

By: Kevin Yank

Kevin Yank — Wed, 11 Apr 2007 02:14:46 +0000

@Grey, Yes, that approach is mentioned in the article above:

If you can’t figure out an appropriate target for the link, however, you can always insert the link into the page dynamically using JavaScript, so that it will not be present when JavaScript is disabled. If you do this, you can safely point the link just about anywhere ("#" and "javascript:;" are common choices).

By: Grey

Grey — Mon, 09 Apr 2007 01:16:01 +0000

If you use “addEvent” anyways, why don’t you rewrite the “addEvent” function to also mutate the element?

Thus, every time you add a click-event, you mutate that element to become a link (or child of a link). No need for markup hacks and you don;t need to remember do to that every time…

By: Kevin Yank

Kevin Yank — Wed, 04 Apr 2007 23:48:24 +0000

Thanks, Sojan80. The book continues to schedule and looks set for a June release.

By: Sojan80

Sojan80 — Wed, 04 Apr 2007 13:59:17 +0000

Hey Kevin, great article… I’m glad to see someone focusing on this topic myself.

Any news on when the new book is coming out?

By: IanMuir

IanMuir — Wed, 04 Apr 2007 02:57:43 +0000

Accessibility issues like this seem to be on the back burner for a lot of developers working with JavaScript. It’s good to see articles like this showing that it’s really not hard to make DHTML more accessible.

Thanks for the great post Kevin.