Re: Grumbling about bugs - Was: [WIP] ElkArte 1.0 Release Candidate 1 - release notes
Reply #45 –
Click menus are fully keyboard accessible if done properly, so you don't have to require manual targeting via mouse. OTOH, hover menus are useless to anyone who can't use a mouse.
I'm up for usability too. I wouldn't like click menus if I found them bad for usablility, and my reactions and tracking ability are still good enough that I can generally use CSS2 drops without problems (ie: no delays on anything). Personally, I don't find click menus at all bad for usability. I find them to be fast and clean in operation. It's not as if I'm advocating a system I wouldn't use myself.
Re: Grumbling about bugs - Was: [WIP] ElkArte 1.0 Release Candidate 1 - release notes
Reply #47 –
Yes you can, because this menu runs js that allows you to do that. Nao was talking about droppies with no js (not so good for keyboard a11y).
ETA: You can get limited keyboard a11y without js, but you have to mess around with focus a lot and it gets rather tricky.
Re: Grumbling about bugs - Was: [WIP] ElkArte 1.0 Release Candidate 1 - release notes
Reply #48 –
Come to think of it: if you want to use hover menus, but still provide decent a11y for people with less than perfect reactions and tracking ability, what you should be doing is using a long mouseout delay combined with the click-anywhere-to-close functionality that most click menus offer. This is a bit of an oversight in Superfish, and might be worth mentioning as an issue.
If Superfish had the same click-anywhere-to-close as is offered by Superclick, you could use a long mouseout delay while still having the ability to clear the decks instantly if things started getting all messed up.
Re: Grumbling about bugs - Was: [WIP] ElkArte 1.0 Release Candidate 1 - release notes
Reply #52 –
Work here.
What (crappy) browser?
Re: Grumbling about bugs - Was: [WIP] ElkArte 1.0 Release Candidate 1 - release notes
Reply #53 –
Crappy Firefox on crappy Windows 7 64 bit here.