RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Hi Mathew, http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp I have a bug report... tested against FF 3.6.4 and IE6 (no bug under Chrome 5.0.376) Steps to reproduce: - click on background - tab to focus first menu item - hit enter to display sub-items - tab through to

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Sorry Thierry I only took a quick look at the page and didn't read it fully. Mike -Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Thierry Koblentz Sent: 29 June 2010 17:34 To: wsg@webstandardsgroup.org Subject: RE: Using CSS

Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

On 29 Jun 2010, at 00:30, grant_malcolm_bai...@westnet.com.au wrote: I'm trying to avoid use of Javascript due to accessibility concerns. Trying to shoehorn functionality (which is what JS was designed for) into CSS (which is designed for presentation, not logic) is not good for

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Hi everyone, Can everyone suggest which CSS/JS horizontal and vertical drop down navigation they would recommend? Thanks, Elaine Wildash Web Dandy Twitter: http://www.twitter.com/webdandy www.twitter.com/webdandy Facebook: http://www.facebook.com/pages/Web-Dandy/171945798743

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

I find it's best to do your homework, and shop around. There are so many options and paths you can go down, and with things changing rapidly so often, something that works today, may not work so well tomorrow. Sitepoint is a good start, they publish a good book By Rachel Andrews, CSS Anthology,

Re: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

I used to use cssplay menus 6+ years ago but they're not the friendliest or most compliant to work with. I really like superfish - i've been using that for a few years with no problems at all. and I find it very easy to customise. http://users.tpg.com.au/j_birch/plugins/superfish/ I

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Try this for CSS menus with keyboard support: http://carroll.org.uk/sandbox/suckerfish/bones2.html This menu may be accessible, but is it usable? Unless I am missing something, keyboard users need to go through *every single link* in the menu to reach the last item :-( I have these two:

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Hey Thierry, Sorry to say this but the keyboard friendly version: http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp Only fires, via keyboard, on Articles E-K in IEv8 or Firefox. Mike -Original Message- From: li...@webstandardsgroup.org

RE: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Hi Mike, Sorry to say this but the keyboard friendly version: http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp Only fires, via keyboard, on Articles E-K in IEv8 or Firefox. This is by design. Keyboard users could not reach these pages if they were not focusable at least

Re: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu)

Sorry to say this but the keyboard friendly version: http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp Only fires, via keyboard, on Articles E-K in IEv8 or Firefox. This is by design. Keyboard users could not reach these pages if they were not focusable at least from