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

g 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.

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 th

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

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 l

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

[mailto:li...@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/b

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: ht

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

It seems I should have added my standard disclaimer that I don't personally use code that requires a browser hack to work, even if it was on a site I recommended. =) Whenever I have gone there for inspiration, I have had to modify the code/css to suit my requirements. I assume that's normal

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 haven't

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

David Dorward wrote: * Can't respond to navigation without a pointer (e.g. keyboard tabbing, or a breath switch) But adding :focus as well as :hover is easy enough. * Can't have any 'fuzz factor' around the pointer position and timing of when a menu goes away But you can have the basic m

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

PM 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

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 taken a quick look, I'd run a mile from them. The first one I looked at was missing and pointed me somewhere else

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

I'd recommend using one from http://www.cssplay.co.uk/menus/ The trick is deciding which one to use, really. =) HTH, -Delos On Jun 29, 2010, at 4:23 AM, Web Dandy wrote: Hi everyone, Can everyone suggest which CSS/JS horizontal and vertical drop down navigation they would recommend? Than

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: www.twitter.com/webdandy Facebook: w