THE SHORT ANSWER
This is a preliminary check, not an accessibility certification. Test a real public route, record what happened and keep the result limited to what you actually checked.
Choose the route before touching the keyboard
Start from an ordinary public page and name the task. For example, reaching the contact form from the homepage is a clear route to test. That is a suggested exercise, not a claim that your site currently has a problem.
Use a desktop or laptop browser and note its name. Keyboard behavior can vary with the device and settings, so check the current instructions for your setup if controls are not included in keyboard movement as expected.
Do not begin halfway through a staff account and call that the customer experience. Check the page a visitor can actually reach without your knowledge or permissions. Avoid private account screens in any recording you make.
Keep the scope modest. You are looking for obvious barriers to report, not proving that every page works for every person. Asking somebody to imitate a disability is not a substitute for a proper accessibility evaluation.
Follow where the focus moves
W3C's Easy Checks guide describes moving through page controls with a keyboard and checking for visible focus. Try Tab to move forward and Shift with Tab to move back, as appropriate for the browser. Notice which link or control is selected.
If the indicator disappears, record the last place you could see it. Check whether a banner or other content covers the selected control. A control may be present without making its position understandable to the person using it.
Follow the contact link and any menu needed to reach it. Do not assume a menu works with the keyboard because it works with a mouse. Test the actual controls, without trying to repair their code during this first check.
At the form, see whether you can reach its controls and understand their labels. W3C's instructions distinguish proper labels from placeholder text. A hint that disappears as somebody types should not be the only way to identify what the field means.
Coordinate before testing submission. You can inspect the route without sending an inquiry. If a real submission is needed, use details you control and clearly identify it as a test to the person who receives it.
Write down what failed, not a guessed diagnosis
Give the developer the page and exact steps. A useful report might say you moved from the homepage contact link to the form, then could no longer see the selected control. Replace that example with what happened in your actual test.
Include the browser and any relevant keyboard settings. An unexpected result needs investigation; it is not automatically proof that the site is solely at fault. The aim is to make the behavior repeatable for somebody who can check the implementation.
A short recording or screenshot can help if it shows the relevant control and contains no private information. Describe what the image establishes rather than claiming it proves a complete accessibility failure.
Ask for the cause and proposed correction. Do not insist on changing an outline color when the control is missing from keyboard movement altogether. A cosmetic adjustment and a functional repair are different jobs.
Keep the result honest
W3C describes Easy Checks as a first review. Passing these checks does not establish that a site is accessible. A broader evaluation needs other checks and appropriate human review, including relevant assistive technology testing.
Do not turn this exercise into a legal compliance badge or a promise that every visitor can complete every task. You can accurately say that a particular route worked under the recorded test conditions. That is the evidence you have.
After a repair, repeat the original steps. Check ordinary mouse and touch use too, and retain the notes for the next relevant website change. There is no reason to lose a useful test just because the immediate issue was fixed.
For planned work with Your Page, put the route and observed barrier in the brief. A specific problem with reaching the contact form gives the discussion a starting point. Leave legal or certification claims out of the request unless they are part of a properly defined professional assessment.