tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 19 January 2010

Against Vertical Navigation

Posted on 07:30 by Unknown

There is a well written post over at Smashing Magazine by Louis Lazaris titled The Case Against Vertical Navigation. I have made this argument to my own clients (and other web professionals) many times, often with feedback that implies the client knows how users actually surf. This article wraps up the same points I've made and provides some pretty screen captures. The core points follow...

It Discourages Information Architecture

Using a content management system is the best way to demonstrate how true this is. Sites are no longer made up of a few top pages and perhaps one level of sub-pages. A well-structured press section (with archives and categories) will blow up a left-side navigation structure pretty quickly. It also encourages site authors to keep adding top-level pages until the navigation bar is too long to be useful.

It Wastes Prime Screen Real Estate

So much of the valuable page real estate is taken with vertical navigation that the site will miss out on key promotions or cross-links, partly because authors get more cavalier about the length of words when they are stacked in a column. On longer pages, often the entire column is wasted with dead space below the navigation.

It Doesn't Conform to Real-Life Reading

Vertical navigation results in shorter line-lengths for content, especially if you add images, pull-quotes, cross-sells, blogrolls, and so on to the other side of the page.

Fly-Outs Aren't as Usable as Drop-Downs

Many clients opt for fly-out menus to alleviate the issue with multi-tiered sites, but users don't navigate them as well as fly-outs from a horizontal menu (what the article calls drop-downs). Not only is it physically more of a challenge with a narrower active area, but adding another level gets even more complex for users.

It's Not as Successful, According to Studies

Our own user group studies have shown this, and the article references some research and shows some heat maps that indicate where users look on a page.

The Few Benefits Are Negligible

Having very long names as the primary navigation links can seem like a benefit, but in reality users don't read the entire text, they just parse it for the nouns or action words. The ability to have as many links as you want is also a detriment as users eventually can't keep track of all the options.

Exceptions to the Rule

The author does provide some examples where this rule can be broken. There are some screen shots worth checking out that support the exceptions.

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in design, usability, UX | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Social Media Day 2011 in Buffalo #smdayBUF
    Last night marked the second Mashable-sponsored Social Media Day here in Buffalo. With 154 RSVPs for the event, the venue, The Eights Bist...
  • Web Accessibility Sorta-Infographic
    WebAIM is a non-profit organization within the Center for Persons with Disabilities at Utah State University. It has a reputation (perhaps o...
  • Now the Mobile Web Is Dead?
    It was barely two years ago that I scoffed when Wired declared the web dead ( Enough about the Death of the Web ). Fast forward to today and...
  • Browser Performance Chart
    Jacob Gube has posted a handy chart over at Six Revisions titled " Performance Comparison of Major Web Browsers ." He tests the c...
  • Facebook, HTML5, and Mis-Reporting
    My Twitter stream and the headlines of sites across the web yesterday lit up with Facebook's CEO blaming its stock price (failure to mee...
  • The Science of Trust in Social Media
    I am one of those people who always needs to see proof of some assertion, evidence to back up a claim. While I can accept anecdotal evidence...
  • ICANN Moves .org Away from VeriSign
    This Saturday, the .org top-level domain (TLD) will no longer be privately managed. With VeriSign's contract with ICANN for management ...
  • Speaking at Mom 2.0 in Houston, TX
    I will be in Houston this week to speak at the Mom 2.0 Summit (Feb. 18-20, 2010, Houston, TX). To make it a little easier to describe, here...
  • Algonquin Studios Gets Local Press
    I'm taking an opportunity to brag a little about my company, Algonquin Studios , being featured today in the Business section of our lo...
  • App Store Meta Tags
    Why yes, Dominos, I'd love to tap again to get your real home page to order a pizza when I could have done it right here, below your ove...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ►  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ►  April (8)
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ▼  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ▼  January (11)
      • Too Soon to Advocate HTML5?
      • Define "Cognitive Disability"
      • Mashable on the Web of Tomorrow
      • Mobile Internet Use Continues Climb
      • Firefox 3.6 Is Here
      • Accessible Video and Transcripts
      • Against Vertical Navigation
      • The Latest on HTML5
      • W3C: Contacting Organizations about Inaccessible W...
      • Article: Lots of Twitter Followers Guarantees... N...
      • ALL-CAPS: Harder to Read?
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile