Expose nested navigation without losing the parent context

What to change

Choose a nested navigation pattern that clearly names the current level and offers a predictable route back one level.

A worked example

Illustrative example

A visitor inside Services then Rehabilitation sees that context and can return to Services without closing the menu and rebuilding the path.

How to check the result

Accept when every level identifies itself and provides working routes both to its parent and out of navigation.

A mistake to avoid

Using an unlabelled arrow for every return action leaves visitors guessing whether it means parent, previous page or close.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordOpen the deepest mobile navigation branch and inspect its heading and return control. Identify which parent the return action will reveal before using it.Navigate down and back up with a keyboard. Ask the supplier to demonstrate the focus destination and how a screen reader distinguishes each panel.Close the entire menu from a deep level and reopen it. Check whether the chosen reset or retained state is understandable and consistent.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.