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

2010-06-30 Thread Thierry Koblentz
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)

2010-06-30 Thread Foskett, Mike
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

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

2010-06-29 Thread Web Dandy
www.facebook.com/pages/Web-Dandy/171945798743 _ From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of David Dorward Sent: 29 June 2010 07:15 To: wsg@webstandardsgroup.org Subject: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu

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

2010-06-29 Thread John Stericker
To: wsg@webstandardsgroup.org Subject: Re: Using CSS instead of JS for accessibility (was Re: [WSG] CSS Expandable Menu) On 29 Jun 2010, at 11:04, de...@littlegent.com wrote: I'd recommend using one from http://www.cssplay.co.uk/menus/ The trick is deciding which one to use, really. =) Having

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

2010-06-29 Thread daniel a. thornbury
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)

2010-06-29 Thread Thierry Koblentz
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)

2010-06-29 Thread Foskett, Mike
...@webstandardsgroup.org] On Behalf Of Thierry Koblentz Sent: 29 June 2010 16:22 To: wsg@webstandardsgroup.org Subject: 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

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

2010-06-29 Thread Thierry Koblentz
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)

2010-06-29 Thread Mathew Robertson
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