Navigation

1. Introduction

Effective navigation is essential to ensure that users can easily find information and complete tasks on government websites. Navigation must provide a clear, consistent, and intuitive pathway through content, regardless of how users arrive at the site.

For government websites, navigation is not only about structure—it must support service delivery, enabling users to complete key tasks quickly and efficiently.

Navigation design must prioritise:

  • User needs and top tasks 
  • Clarity and simplicity 
  • Accessibility and inclusivity 
  • Consistency across government platforms 
  • Mobile-first usability 

 

2. Core principles

2.1 Task-based navigation

Navigation must prioritise what users want to do, rather than how government is structured.

  • Use action-oriented labels: 
    • “Apply for a passport” 
    • “Register a business” 
  • Avoid department-based labels unless necessary 

2.2 Simplicity and clarity

  • Limit main navigation items to 5–7 items 
  • Avoid deep hierarchies (maximum 3 levels) 
  • Use familiar, user-friendly language 
  • Avoid jargon and internal government terminology 

2.3 Consistency

  • Maintain consistent navigation across all pages 
  • Ensure placement, style, and behaviour of menus do not change 
  • Use consistent naming conventions across departments 

 

3. Navigation structure

3.1 Primary navigation (main menu)

  • Display prominently at the top of every page 
  • Include the most important user tasks and sections 
  • Keep items concise and clearly labelled 

3.2 Secondary navigation

  • Used within sections to show related content 
  • Helps users explore subtopics within a category 

3.3 Utility navigation

Must be visible on every page and include:

  • Search functionality 
  • Contact information 
  • Language selector 
  • Accessibility tools (where applicable) 

3.4 Footer navigation

The footer must include:

  • Contact details 
  • Privacy policy 
  • Terms of use 
  • Sitemap  
  • Copyright information 

 

4. Search functionality

Search is a primary navigation tool and must be prioritised.

4.1 Requirements

  • Visible on every page (preferably top-right) 
  • Include a recognisable search icon 
  • Provide accurate and relevant results 

4.2 Enhancements

  • Support autocomplete and suggestions 
  • Include common or popular searches 
  • Handle spelling variations and synonyms 

 

5. Linking principles

5.1 Clarity and descriptiveness

  • Use clear, meaningful link text 
  • Avoid vague phrases like “Click here” 
  • Ensure users understand where the link leads 

5.2 Consistency and styling

  • Maintain consistent link styles (colour, underline, hover state) 
  • Ensure links are distinguishable from regular text 

5.3 Accessibility

  • Ensure sufficient colour contrast 
  • Provide visible focus indicators for keyboard users 
  • Ensure all links are accessible via keyboard navigation 

5.4 Linking to documents

  • Use the document title as link text 
  • Indicate file type and size: 
    • Example: “Download Annual Report [PDF, 1.2 MB]” 
  • Open documents in a new tab where appropriate 

 

6. Supporting user navigation

6.1 Multiple navigation paths

Provide multiple ways to access content:

  • Main menu 
  • Search  
  • Footer links 
  • In-page links 

6.2 Breadcrumbs

  • Include breadcrumb trails on all pages (except homepage) 
  • Ensure all levels are clickable 
  • Reflect the site structure clearly 

Example:
Home > Services > Identity documents > Apply for ID

6.3 Orientation and wayfinding

  • Clearly indicate the current page or section 
  • Highlight active menu items 
  • Ensure users always know where they are 

 

7. Mobile navigation

Navigation must be designed mobile-first.

7.1 Requirements

  • Use responsive design 
  • Ensure menus are easy to open and navigate 
  • Keep navigation shallow (avoid deep nesting) 

7.2 Touch usability

  • Ensure tap targets are large enough 
  • Provide adequate spacing between items 
  • Avoid overcrowded menus 

7.3 Mobile menu behaviour

  • Prioritise top tasks at the top of menus 
  • Ensure important items are not hidden 

 

8. Long content and page navigation

8.1 Scannability

  • Use headings, bullet points, and spacing 
  • Break content into manageable sections 

8.2 Tables of contents

  • Provide a table of contents for long pages 
  • Include anchor links to sections 
  • Include “Back to top” links where necessary 

8.3 Use of collapsible elements

  • Use accordions for secondary or supporting information 
  • Do not hide critical content in collapsible sections 
  • Ensure content remains accessible to all users 

 

9. In-text linking

  • Use links strategically within content 
  • Avoid excessive linking that disrupts reading 
  • Place links at logical points (e.g. end of sections) 

 

10. Graphic navigation

10.1 Use of icons

  • Use icons to support text labels, not replace them 
  • Ensure icons are universally recognisable 
  • Maintain consistency in icon usage 

10.2 Accessibility

  • Provide text alternatives (alt text or ARIA labels) 
  • Avoid image-only navigation elements 

 

11. Accessibility requirements

Navigation must comply with accessibility standards.

11.1 Key requirements

  • Support full keyboard navigation 
  • Provide visible focus states 
  • Use ARIA landmarks (e.g. navigation, main, footer) 
  • Include “Skip to content” links 

11.2 Standards

Follow WCAG 2.1 AA guidelines.

 

12. Multilingual navigation

12.1 Language support

  • Provide a clear and visible language selector 
  • Keep placement consistent across pages 

 

12.2 Consistency

  • Ensure navigation structure is consistent across languages 
  • Avoid mixing languages within navigation labels 

 

13. Navigation behaviour

13.1 Opening links

  • Do not open internal pages in new tabs 
  • Open external links and documents in new tabs where appropriate 

13.2 Predictability

  • Ensure links behave consistently 
  • Users should know what to expect when clicking a link 

 

14. Governance and maintenance

14.1 Content management

  • Manage navigation centrally through CMS tools (e.g. menus) 
  • Avoid hardcoded links within content 

14.2 Maintenance

  • Regularly review navigation for relevance and accuracy 
  • Remove outdated or duplicate links 

 

15. Measurement and Improvement

Navigation should be continuously evaluated and improved.

15.1 Monitoring tools

  • Google Analytics 

15.2 Metrics to track

  • Most-used navigation links 
  • Search vs navigation usage 
  • User drop-off points 
  • Task completion rates 

 

16. Key principles summary

All government website navigation must:

  • Be task-oriented and user-focused 
  • Be simple, clear, and consistent 
  • Be accessible to all users 
  • Support mobile-first design 
  • Enable users to find information and complete tasks quickly