A responsive menu can look fine in a mobile viewport while keeping keyboard focus on links that are hidden. Before release, test the collapsed and expanded states using a narrow viewport and a physical keyboard.
Check the closed menu
Start at the top of the page and press Tab until the menu control receives focus. Check that its focus indicator is visible. Links hidden inside the closed menu should stay out of the tab order. Activate the control with Enter and verify that its expanded state changes.
Check the open menu
Tab to the first visible link, then use Shift+Tab to move backwards. If your design uses a modal drawer, test that Escape closes it and returns focus to the control that opened it. For a non-modal disclosure, also check that people can move onward to the page content in a logical order.
Test a real user task
Pick one destination, such as a sizing guide. Open the menu, navigate to that link, activate it and check that the destination loads. If the link works but testers repeatedly open the wrong menu section, review the label and the site architecture behind the navigation (guide in Persian by NaslX).
Write a reproducible bug report
Record the browser, viewport, starting state, expected focus sequence and first place it breaks. For example: ‘At a narrow viewport, close the menu and press Tab from the menu button. Expected: focus moves to the next visible control. Observed: focus moves into a hidden navigation link.’
After a fix, repeat the same sequence with the menu closed and open. Keep modal and non-modal expectations separate so a drawer is tested according to its actual interaction model.
Drafted with AI assistance for NaslX.

