Navigation and menus are not a technical matter. They are not confined to the world of IT but are used in real life, too. Navigation is a human interaction matter, human beings with all their issues and problems need and use it. Really successful navigations care about the visitors' needs, not promote a technique or our company's structure. What are we likely to find helpful in our local council office: An index of departments or a list of employees?
The success of a navigation device is largely dependent on how easy it is to use. At any time visitors should be able to find out:
Real life examples are the escalators and elevators in shopping centres.
Up the escalator there is another sign, describing what can be found on this level and where the creature comforts are (information booths, telephones, toilets, changing rooms).
Sometimes this is a map, accompanied by a list of all the shops available on this level. On the other side of the escalator is the list of all the floors again with the current one highlighted.
This kind of navigation works and less successful centres were known to copy from the more successful ones. They make a lot of money, their visitor numbers are high and the shop owners are happy, as the navigation does send them visitors.
The beauty of this approach is its simplicity; we don't overwhelm the visitors with options but give them what is needed at a certain point in time of their journey. Should they want more information, then there are the index terminals and detailed floor maps to help them find out more about "the big picture".
These real life examples can be translated into parts of a web site:
|Real life example||Web site equivalent|
|List of all floors||Main navigation|
|List of all floors with information what to find on each||Homepage|
|Index Terminals||Search functionality|
|Detailed map of all floors||Sitemap|
|Detailed map and list of current floor||Section navigation|
|Information about wheelchair ramps and lifts||Accessibility Statement|
|Information booths||Contact Facility / FAQ|
The very nature of the web and indexing by search engines allows visitors to enter our site at any "floor", and with any technology.
That is why it is a tough call to go with a navigation that needs explanation, or depends on a certain technology. Even testing for the availability of this technology on the home or entry page does not mean visitors won't end up on pages that leave them stranded - they may come from a bookmark, link or search engine results list.
The flip side of the argument of "keeping it simple" is clients: A lot of them love cool navigation and consider their technical environment and experience the standard on the web.
We have some options in dealing with those:
Spotting visitor diversity is a lot easier in a shopping centre. Well trained employees of shops, help desk staff and security can spot if a person needs
On the web, we know nothing whatsoever about our visitors.
Our visitors - the people we depend on to spend money, read our wisdom, or take part in our experiences - could be:
We can use technology to read some of the settings of the browser, but in effect this data does not help us much:
We deal with human beings, not with their technology, therefore the idea of being able to predict what is going on by means of technology is doomed from the start.
We know the right thing to do - we would love to use an easy navigation and spend proper time on the layout, the backend functionality and making it pretty and easy to maintain.
However, we don't do it; instead we tend to spend a large chunk of design and development on the technical implementation of the navigation and run out of time and budget when it comes to cleaning up the code and write maintenance documentation.
The reasons are legion:
This last reason is what should get us thinking. If the navigation is very usable and helpful to some, why not make it their choice to get it?
As an example, let's take multi level dropdown navigation, probably the most common seemingly helpful navigation around.
This kind of navigation is very handy when
A lot of assumptions we have to make. Technology cannot help us with most of these problems. Simply resizing the font shows one of the problems we might oversee when developing this navigation.
Keyboard users will have to tab through all of these links every time they loaded one of the pages, voice recognition users might not be able to expand them, in short - we will have trouble making this navigation accessible. There is a way though.
As there is simply no way to predict the ability of the visitors, the easiest option is to leave the choice to them. The site gets an easy, logical navigation that only shows the options necessary and offers a checkbox, or a button marked "enhanced navigation" with a "what is this" link explaining what it is a about.
Once chosen, this choice can be stored in a cookie or the visitor's profile and there is no need to choose again.If the functionality we need is based on a technology like Flash or scripting, the button can be generated via this functionality, thus never bothering those who don't have the choice to start with.
Following are some guidelines that help determine if our navigation has a chance to be accessible or not. Any time we have to say no there is a problem.
Navigation is one of the most important parts of the site; however, the most important part of a page is the content. If our navigation grabs the visitors' attention and distracts from the content, then it failed its purpose. The content should determine the navigation, not the other way around.
This is easy to forget, as navigation is one of the few things us web developers and designers can play with. At the start of the project we have a rough idea of the sitemap, whereas the content is not always ready or even planned out. It is up to us to tell the client that the content is what people will look for and come for, not how cool or usable the navigation is. The best navigations on the web are the ones we cannot remember, but pointed us quickly to the right place.
If there is a lot of time and budget to be spent, then it should go into proper search functionality and defensive measures - the error pages, warning messages and information pages, not a singing and dancing navigation.