Choose a goal and a clear starting point
Start on a representative page without using a mouse. Define a specific task: open the services overview, find the contact form and prepare a test inquiry. Use fictional details and do not contact real recipients if the environment is not isolated.
Press Tab to move forward and Shift+Tab to move back. Use Enter or Space according to the control. Do not assume every control behaves the same way; follow the interaction the page actually presents.
Track focus and its order
Can you see which control has focus? Does the order follow the page's content? Check that focus does not disappear behind a fixed panel, menu or off-screen edge. Unnecessary stops should not force someone through a long, irrelevant sequence.
Open menus and dialogs. Can you close them predictably? Can you resume where the task was interrupted? Record the step, expected behavior and what actually happens.
Take a form through an error and correction
Submit an empty test form if the environment allows it. Can you reach the error and the field that needs correction? Are earlier answers retained? After a correction, someone should be able to continue without starting over.
W3C describes keyboard accessibility in terms of functionality being operable through a keyboard interface. This practical walkthrough is not a complete accessibility audit or a conformance statement.
Write a finding someone can act on
Example: On Contact, focus moves from the phone field straight to the footer and skips the Send button. Tested with an external keyboard and desktop browser. Expected: the button is reachable after the fields. Add a short reproduction sequence without personal data.
Retest after a fix. Repeat the task at a narrow viewport and with another relevant control. Automated checks can help, but they do not replace following the task yourself.