School website navigation that families can understand

Find the tasks behind the menu

Start with the questions families ask rather than the school's staffing structure. "How do I report an absence?" is a task. "Pastoral administration" is an internal label that may not help a parent find it. Use the language visitors recognise and explain specialist terms inside the page.

Ask the office, admissions team and inclusion staff which information people repeatedly request. Add tasks for families who are new to the school and for visitors seeking governance or policy information. Keep these groups visible without assuming they all need the same homepage journey.

Choose a small set of meaningful groups

A workable starting structure might include About the school, Learning, Parents and carers, Joining us, Policies and information, and Contact. This is an example to adapt, not a mandatory menu. A sixth form or specialist setting may need a different arrangement.

Write the proposed page titles on a simple list and ask colleagues or families where they would look for a task. If several people consistently choose the same unexpected category, change the structure or provide a useful cross-link. Do not force visitors to learn the school's preferred terminology.

Make common tasks directly available

Some information deserves a clear shortcut even when it also belongs in a section. Term dates, absence reporting and contact details are common candidates. Choose shortcuts from actual need, not from the number of stakeholders requesting homepage space.

Keep each shortcut pointed at the main current page. Duplicating the same instructions in several places creates a maintenance problem: one copy changes while another remains wrong. A short contextual link can make a page easy to reach without making a second version of its content.

Distinguish information from actions

A page called "School meals" might explain eligibility, menus, dietary needs and ordering. Make the actual action obvious within that page. If ordering takes place in a separate approved service, explain the transition and give a fallback contact for families who cannot use it.

Avoid a menu made entirely of unexplained system names. Families need to know the purpose of a service before they choose it. The public website should still contain useful guidance when a visitor has forgotten a login or does not yet have an account.

Make menus work without a mouse

W3C's menu guidance stresses clear structure and consistent navigation. A developer should use appropriate navigation markup, meaningful link text and accessible controls for expandable sections. The visible design and the underlying behaviour both matter.

Test opening and closing menus using a keyboard. Focus should remain visible and move predictably. A mobile menu should have a clear label and should not leave hidden items unexpectedly in the keyboard sequence. Hover-only submenus often cause difficulty on touchscreens and for keyboard users.

Check the accessibility guide for a wider task-based review.

Use search as a second route

Search is helpful for visitors who know a word but not its location. It should search useful public content, show understandable results and keep private material out of the index. A result should identify the page clearly rather than show a cryptic filename.

Review common unsuccessful searches when an appropriate privacy-conscious reporting method is available. They may indicate missing content or an unfamiliar label. Do not use search as an excuse to leave the main navigation confusing; many visitors will still browse.

Help visitors know where they are

Use clear page titles and, where the structure benefits, a breadcrumb trail back to the relevant section. Long pages can include a list of section links. Related guides should connect genuinely useful next steps rather than fill space with arbitrary recommendations.

For a school within a trust, distinguish school-specific information from trust-wide information. A parent should not have to guess whether a policy applies locally or across the organisation. Label shared material and make the route back to the school understandable.

Test journeys before and after launch

Give testers realistic prompts without telling them where to click: find next term's start date, report an absence, locate support information or identify the complaints starting point. Observe hesitation, unexpected choices and dead ends. Record whether the task was completed, not just whether the menu opened.

Repeat a few tests on a phone and with a keyboard after navigation changes. Improve the structure using those observations and the content audit. A stable, understandable menu is more valuable than frequent visual rearrangement that makes returning visitors relearn the site.