I'd be interested to hear of examples or ideas like that as well.
I think the best improvement I've seen is to disable scrolling after
a user clicks an item from the dropdown. Since focus remains on the
dropdown, scrolling often becomes a problem, especially for web pages
/ apps, since scrolling
Jared mentioned that a sasquatch footer might be an indication
that your site lacks sensible / complete navigation elements. That
could definitely be true.
But, I think that precludes the case where the footer area serves as
an instant browsing tool. It's true that many users are on the site
for
Some of us seem to be assuming that the footer contains a site map,
straight up. And others are assuming it could be that OR a context
sensitive area for calling out interesting or related material /
resources.
I'm not thinking about lost users at all - if a user is lost and
needs a site map,
If it were indeed a site map, then I would suggest linking to it from
a top-level navigation area. There are more users familiar with a
typical site map link than with scrolling to the bottom of the screen
to find it there.
If it is not just a site map (perhaps containing additional material
in
We have a similar problem for a complex web application. The approach
we have taken is to ensure that legacy tools are migrated whole,
rather than piecemeal, and we keep the global navigation consistent
in all cases, which we hope provides a familiar framework for users.
Local navigation is
