Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: incrediBILL
But what if your host and hostess pointed you to their refrigerator and said, "Help yourself".
That's the way I feel when a website hands me one of those danged mouseover dropdown css dhtml menu system thingies. It's like they don't think enough of me to organize their groceries into a decent meal, they just tell me to hit the kitchen and fend for myself.
I put the mouse over a promising, top level menu choice and -- FLASH! -- no, I can't click there: something else pops up with a bunch of words on it. Then I accidentally move my hand a smidge while I'm trying to read the interloper, and now the thing vanishes.
Not only must I raid the fridge, but now the contraption has a broken hinge and the door slams on my fingers. So I put a low level cramp in my wrist, just to make sure that I don't move my hand whilst my eyes are trying to take in the choices. Happy dinner party.
I don't know the name of the clever geek who created the first one of these, but I'll guarantee you it wasn't a marketer, and it wasn't an Information Architect. The mouseover options do a lousy job in both those departments.
No, the inventor in this case had to be a code-freak, a total techie strutting their stuff, a major show-off of an IT ego.
And I'll tell you something else. Just look at the menu choices the next time you land on a site with one of these little contraptions. Are the categories arranged the way you think, as an outsider? Or are the slices of information more the way the organization thinks about itself, internally.
I'll bet you it's the latter -- but a good IA would be created around the former. If you care about your guests, you don't throw every possible ingredient at them on every page in fear that they might miss something.
Instead, you slice, dice and organize your stuff into bite sized goodies that make sense to a visitor's palate. A menu that allows them to choose a tasty, intuitive path to whatever they need. You create a coordinated meal, a banquet even, with maybe a chance to find an unexpected but tasty side dish along the way.
This rant was stimulated by a recent professional event - my second chance to remove a mouseover menu from an already functioning site, and measure the results. This time, the Home Page with DHTML had a 45% abandonment rate -- 9 out of 20 visitors were one hit wonders. Remove the DHTML menu and guess what? The abandonment rate fell nearly in half.
My earlier experience saw a 32% increase in page-views per unique with a similar change. And then we went to work on the IA and it got even better.
Mouseover menus? Please Say NO!
... the ones I really hate are those that disappear as soon as you try to get the mouse near enough to them to click something - probably caused by the text size rendering differently from the original design.
The ones I like are those that pop-up on a complex site to tell you what subjects are covered by the link you are hovering over. This is really helpful if you are tracking down something very specific, because you don't have to wait for the link to resolve to see if what you want is on it.
a promo for Jakob Nielsen?
Well, I would consider Jakob good company -- he can do a promo for me any time he wants to -- but he wasn't on my mind when I wrote this
As I mentioned, I've recently been in the trenches with several clients on this issue. It took a LOT of data to convice them to let me to try something else, because they were in love with their gizmo.
Simple fact is, it just didn't work. So I thought about this some more (I just know I'll see this battle again in my future) and tried to come up with an easy-to-get metaphor for the way I see the situation.
I think one of the biggest problems for many sites is that someone, somewhere, is trying to show off instead of trying to serve their audience. And mouseover menus are a classic example.
I would consider Jakob good companyAs would I. Many a gem I have found on his site.
because they were in love with their gizmo.That's because they never need you use them.
Simple fact is, it just didn't work.Sure it did. The problem wasn't that it didn't due what it was designed to do, the problem was it wasn't designed to do what it needed to do.
easy-to-get metaphor for the way I see the situation.Unfourtunatly it still requires them to think, but at least not as much.
trying to show off instead of trying to serve their audienceIf you know you're good, you'll also know that your work will speak for itself without fanfare, and to the right audience. It's when you lack self-confidence, or think you're better than you are, that you run into trouble.
Then there are those who are only out to make a quick buck. I see myself as a craftman, and I take pride in a job well done.
On one site where I saw the approach used well, it was just a small div that popped up on the word "Utilities". The DHTML menu extension provided a choice of about 5 utility functions that regular users of the site would need close at hand -- but that would have cluttered the layout in most situations.
I think that these dynamic menus should be looked at in the same way as Flash - there is a time and a place for them, but make sure that you've done your research and it is the time and the place for them! Like Flash, DHTML rollover menus were used on almost every site for a time, in most cases there was no need for them, in some cases it was just designer/developer ego: "look at how good I am with my fancy menus".
However, I think that if developed properly this type of menu system can be most effective (remember, the major OSs all use cascading menus - so users know and understand them). One of pet hates of mine with these menus is (1) when the menu hover state is only the link text, so hovering anywhere off this and the menu disappears!
In my early web design days I thought they were cool. I also thought it cool to do other mouseover tricks.
Today I barely use any mouseover at all. It's a maturation.
One site which I visit frequently though (designed by a guy who THINKS he is a technology expert - still thinks FileMakerPro is the greatest database ever) recently abandoned his DHTML drop menus in favor of..... Java Applet drop menus. What a bloat. I had a good laugh.
I really think that there are two issues here, and the primary one is a well considered information architecture, not the visual rendering. It's just that so many of the trendy cascade menu sites seem to have given little attention to their IA.
and the primary one is a well considered information architecture,
I couldn't agree with you more. One of the major failings of many sites is that they stumbled at the first hurdle and never did and Information Architecture study for the site. And you are quite right, these menu systems just get choked up with ineffective lists of links because of this.
There is an interesting update link at the end of the SURL article which makes some interesting follow up points.
... Cascading menus move us into the nasty territory of nesting and hierarchies. Hierarchies are so natural to the mathematically inclined, but they are quite unnatural to the rest of us. The temptation to make menus hierarchical is nearly unavoidable for most programmers ...
I think that this point also shows that without any shadow of a doubt that an IA is invaluable. I firmly believe that you cannot create a usable site without first having established an IA for that site.
Verticles on the other hand are much better. They seem to not have that problem. It is a natural appearance for info to pop down under the main button.
I also think linking the main button and not rendering it unusable is a must. Don't have the menu cover the button. Link it to the top directory and have the sub links be just that, secondary.
Today I barely use any mouseover at all.It all depends if they add to usability or detract from it. There are some CSS mouseovers I happen to like on menus. I usually change the color, maybe reverse the justification (from left to right), possibly change the font weight and/or style, and occasionally change the borders. In all cases it helps by highlighting which link is being pointed to and that there is a link being pointed to. It basicly enhances the behavior of the default style of links. (Discribing it makes it seem like a bigger deal than it is.) There is a CSS trick I saw which I'm thinking of trying if I find the right place. I've seen where some additional informitive text (or image) is displayed under the menu. But I'm not going to add it just to add it, I would only add it if I thought it was benificial.
The bottom line is if it add to usability and/or accessability, then why not? If it detracts, why yes? In neither adds nor detracts, then to each their own.
I just went to a vertical, mouse over nav bar - primarily because things were getting too cluttered in the header. Feedback has been fairly positive, though there have been some people, like my mom :) , who have been completely bewildered by it.
I'm hoping that more and more folks will switch to this type of navigation, so that the learning curve of what to do when menus disappear or appear unexpectedly gets accelerated.
From the perspective of making efficient use of space, the mouse over nav bar is a godsend, though.
Have you any experience of how Yahoo deals with sites with this kind of menu with regards to their ludite 'submission/acceptance' policies.
I am always wary about using this kind of functionality (even if there is a valid reason - usually the client insisting on it!) if an entry in Yahoo is also required.
I haven't used Business Express for a while - what's the situation now?
we have submitted several sites with vertical dhtml menus to various yahoos and have never received any negative feedback.
we do have bog standard text links in a left hand nav bar as well, so the dropdowns are there to help regulars go quickly to the bits of the site they like best.
still a lot of food for thought tedster :-)
Here's the thing that gets me the most. Usually when you mouse over one of these menus and you click on the "master" section name (like "about us"), it's not even a link. Only the exposed submenus at hot.
Like was said before, hopefully this will go where Flash has gone - find the right context.
As soon as I see a site with menus that light-up, scroll, levitate, shimmer, do back-flips or otherwise demonstrate how clever the designer was in spending the clients' money on such useless eye candy, I am reasonably sure that the focus of the site will be on "pretty" and not architecture or substance.
But, I would the first to agree that large sites with a natural heirachical structure are often best served by a logical drop down heirachical menu. A simple menu array in a css file will do the job and serves the viewers needs quite adequately.
The KISS principle is still alive and well. Its a pity more people have never heard of it.
Let's be clear, the problem isn't with dhtml, it's the decision of when to use it or any other fancy gui when it's not necessary and it interferes with the ability to use the site.
That's what usability is all about, common sense, understanding of your customers needs/wants/hates, and communicating with them to attain it, not just doing a marketing test.
That's a common problem, usability sounds so un-cool, or un-trendish, or un-fadish.
Who cares if it is cool, the important thing is if it is USABLE by the customer.
Like decisions to have a dhtml popup instead of a regular one, based on the stupid idea, of making sure people see the popup.
We must be accurate in our determination of when to use what technologies.
Additionally, the forms double up as a page marker, allowing readers to see the category and subcategory of the page they are visiting.
joined:Oct 27, 2001
But what I really dislike are mouseover links where the text changes size when touched. I can handle color changes, but having the type jump to a larger size is distracting and annoying.
Yaaay .... and I thought it was just me!
I groan when ever I land on a site using DHTML mouseovers, and here in Oz, it seems the various .gov.au designers are exceedingly fond of them.
I can only recall one instance where it was in use and it didn't get in my way. What must it be like for people with accessability issues?
That Tedster is able to provide tangible "proof", by way of before and after %s, helps.
Another "oohh aah bells and whistles" feature I hope can only go the way of <blink> and other such geegaws, as soon as possible.
BTW, excuse me for being thick (cold, cough, stuffy nose, no caffeine yet today ... whatever ...), but what does IA mean in this context?
Oh, Information Architecture ... just read the rest of the thread ... : # )