Mobile menus for B2B websites: checking the journey from opening to destination
Plan mobile menu expansion, focus, navigation and tests on phones and keyboards, from finding a service to returning to reading.
Article language: English

In this article
A menu icon looks harmless: three lines and done. Only after opening it do you learn whether a customer can find a service, distinguish a link from an expandable group and return to reading. A good phone menu must support that whole journey. A full-screen panel can be beautiful, but if it cannot be closed, an invitation becomes an escape room. Check its behaviour before judging its appearance.
Designing menu behaviour requires decisions beyond drawing a site map. Here we focus on opening, expanding, closing and testing mobile navigation. This practical acceptance plan can be given to the designer and developer before animation work begins.
What should the menu help people do on a small screen?
Choose the main journeys: finding a service, checking the company, reading a guide and starting contact. Record the starting point and expected destination. Include someone entering directly on an article, not only a home-page visitor. A menu often helps people regain their bearings after such an entry.
Review labels with someone outside the company. Does “Expertise” mean services, the team or technology? A phone leaves little room for explanation, so shorthand can cost extra submenu openings. If the problem is the division of content itself, revisit B2B information architecture (in Polish).
Do not assume every item needs equal prominence. Contact and support for an existing customer may lead to different actions. Set priorities according to business tasks. Keep less frequent but necessary information accessible instead of removing it merely for a calmer composition.
Is a simple panel enough, or are several levels needed?
A simple expandable panel may suffice for a short list of pages. A larger offer may need groups and overview pages. Every extra level increases the effort of staying oriented: people must remember where they entered and how to return. Justify each level by the actual organisation of the offer.
On a phone, a large desktop menu should not simply be squeezed smaller. Decide whether groups expand in place or open a separate view. In the latter, show the current group name and a clear way back. In the former, check list length after several sections are opened.
Decide how the overview page works too. A category name can be a link while a separate button expands the submenu. If the same element sometimes opens a list and sometimes navigates, customers must guess the rule. Make an explicit design decision and apply it consistently to similar sections.
How do people distinguish navigation from opening a submenu?
A link leads to an address; a button changes an interface state. That distinction should also be available to people using assistive technology. The expansion label needs to identify its section, and the open state should be conveyed programmatically, not only through a rotating arrow.
W3C's disclosure navigation example uses buttons to reveal lists of links. It also explains why ordinary site navigation does not automatically need the ARIA menu role. It is an example to assess and test, not ready-made proof that an implementation is accessible.
In the mock-up show at least the closed state, open state and active page. Describe what happens on a second press and when moving to another section. Without these states, the team ends up completing the design in the browser and making unagreed decisions while coding.
How should closing and returning to content work?
People should easily close a menu opened by mistake. The close button must remain available with a long list and enlarged text. If tapping the background can close it, retain an explicit button too. The gesture alone does not explain the option to someone unfamiliar with it.
Decide whether the panel is an ordinary expansion of the page or a modal dialog that blocks further interaction with it. That choice determines focus rules: which element is currently operated. Do not mix the two patterns without checking the consequences for keyboard and screen-reader use.
After closing, customers should return to a logical place. Test opening the menu halfway through a long article. The page should not jump to the top or lose the reading position without reason. Small problems like this can recur on every navigation attempt.
How should screen height, scrolling and orientation be handled?
A phone's available space changes. Browser bars may hide, the on-screen keyboard takes part of the view, and rotation changes proportions. Check the menu in portrait and landscape, including on a shorter screen. Do not limit acceptance to one wide phone model.
A long list must scroll to the end without losing access to close. When the panel covers the background, decide what a gesture scrolls: menu, page or both. Accidental scrolling beneath the panel can make it hard to return to the interrupted reading position.
Also resize a desktop window. The mobile state should not leave hidden locks after switching to wide navigation. Press several links quickly and use the back button. These checks complement whole-site acceptance (in Polish), because a fault often appears only between pages.

How can labels stay readable and targets easy to hit?
Test the longest real names rather than designing around short examples. A label should fit without hiding an important distinction. Two lines may be better than aggressive shortening, but require suitable spacing. Closely placed expansion buttons must not cause accidental choices.
Clearly show the current section. Colour can help, but add another legible indicator. If the menu includes languages, use understandable names. A flag alone does not always identify a language and can suggest a market the site does not serve.
Check the typography system (in Polish) with enlarged text. A line height that is too small or a fixed button height can clip characters. A menu is no place for decorative text that takes effort to read. Brand expression can remain in proportions and materials without making a simple choice harder.
How can animation support orientation?
Motion should explain a state change. A short expansion can show the relationship between a section name and its links. A long performance on every opening adds waiting to a repeated action. Decide when elements become available and what happens after a quick second press.
Check the reduced-motion preference. Navigation must remain understandable if a transition is shortened or replaced by a calmer change. Do not make clicking depend on the end of a decorative sequence. A real-device test will show whether movement remains smooth with a long list and a heavier page.
The microinteractions guide (in Polish) discusses detailed rules. In the menu specification add your own tests for interrupting animation and navigating while it opens. These situations distinguish a controlled interface from an effect that works only in a calm demonstration.
What might a hypothetical consultancy menu test look like?
Imagine a consultancy with three service areas, guides and contact. This is hypothetical. A person arriving by recommendation opens an article on a phone and looks for a service matching their situation. The menu shows general section names, but the person does not know which to choose.
The team adds short group descriptions and overview pages. In the next task, the user reaches the right service, but on returning the menu remains open and covers the text. The team records this as a behaviour defect even though the navigation goal was reached earlier.
The developer fixes the state after navigation and repeats the test with several quick clicks. The company records finding the service and handling the return separately. Separate assessments help choose a fix: there is no need to rename the section again if the only problem is closing the panel after navigation.
How should you test with people outside the project?
Give a task in the language of a need without naming a tab. “See whether the company can help with this process” reveals more than “go to Services”. Observe first choices, hesitation and going back. Ask what the person expected after clicking, without suggesting a route. A moderated prototype usability test (in Polish) describes recording the facilitator's help separately from the participant's independent journey.
Record a problem with its conditions: device, entry point, open groups and where the mistake happened. “The menu is unintuitive” makes a fix hard to choose. “The category name looks like a link but only opens a list” gives a concrete direction. After a change, repeat the task with someone who does not know the previous version if possible.
Complement observation with a keyboard test and a basic accessibility review (in Polish). A small qualitative test helps find barriers but does not justify statistical claims about all visitors. Report what was actually checked and which device combinations remain to assess. A further step can be research with people using assistive technology (in Polish), preserving their usual way of using the site.
Also test opening the menu while filling in a form. A person may want to check a service before sending a question. Opening and closing the panel should retain the entered message. If navigating to another page removes data, consider a solution suitable for the whole form and test it separately.
The menu should not pretend navigation is finished while new content is still loading. A clear waiting state and a way to retry help on a weaker connection. Run the test without a prepared browser cache: a first-time visitor has different conditions from a developer opening the same pages all day. Recording test conditions lets the team reproduce a problem honestly later.
The menu leads to a section, but people still need orientation after entering details. Where there are several levels, check breadcrumbs (in Polish). Their job is to show structure; they need not reproduce every earlier page a person visited.
How do you accept the finished menu and close the scope?
Check at least:
- Important tasks have a clear entry from any page.
- Links and expansion buttons convey different functions and the current state.
- Closing works and returns people to reading without losing their place.
- A long list scrolls while the close button remains available.
- Rotation, zoom and width changes leave no locks behind.
- Quick clicks and the back button do not leave the panel stuck.
- The reduced-motion version retains full operation.
Include menu conditions in your website project brief. The guide to preparing a website brief (in Polish) can help you specify them. To combine a distinctive visual identity with convenient navigation, see Aeneia Design.







