Christian Heilmann

What can we do when there is too much navigation?

Thursday, July 28th, 2005 at 9:58 pm

We have faced quite a dilemma today and had a 4 hour meeting about possibilities how to solve it. The client has a huge sitemap, and they are bound by law to offer all of the services listed in it on their site as links.

Now, up to two levels, a navigation on the left hand side is bearable, but when it comes to three levels with up to 30 links each, even the highest resolution will have the current link below the proverbial fold.

We tackled a lot of that by using something I christened “Contextual navigation order (CNO)”, meaning the current section will always be the first in the navigation, which is good for visual users and screen readers, as neither need to go past the other links to reach where they want to go. An example of CNO is on the easynav demo page and on the North Yorkshire Council web site. North Yorks solved the third level by moving it to the right of the screen, but in this case that space is reserved for marketing.

As cutting down on links is not an option – although it would be more usable – we needed a solution that shows the third level. As the client was not sure if their development team can put parts of the navigation somewhere else on the screen – the easiest option in the CMS (Tridion) is to loop through all folders once and generate one navigation – we wondered if there is a CSS/JS solution which still remains accessible.

A first draft of my attempts can be found here:

Maybe you will have to face the same problem, or you have another option?

Personally, I don’t see much sense in displaying that many links at once, and as a visitor I’d use the A to Z or the search instead.

Share on Mastodon (needs instance)

Share on Twitter

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

Dev Digest 146: 🥱 React fatigue 📊 Query anything with SQL 🧠 AI News

Why it may not be needed to learn React, why Deepfake masks will be a big problem and your spirit animal in body fat! 

Dev Digest 147: Free Copilot! Panel: AI and devs! RTO is bad! Pi plays!

Free Copilot! Experts discuss what AI means for devs. Don't trust containers. Mandated RTO means brain drain. And Pi plays Pokemon!

Dev Digest 148: Behind the scenes of Dev Digest & end of the year reports.

In 50 editions of Dev Digest we gave you 2081 resources. Join us in looking back and learn about all the trends this year.

Dev Digest 149: Wordpress break, VW tracking leak, ChatGPT vs Google.

Slowly starting 2025 we look at ChatGPT vs Google, Copilot vs. Cursor and the state of AI crawlers to replace web search…

Dev Digest 150: Shifting manually to AI.

Manual coding is becoming less of a skill. How can we ensure the quality of generated code? Also, unpacking an APK can get you an AI model.

My other work: