Can a customer finish your enquiry form with a keyboard?
An owner’s walkthrough for finding the exact point where a real enquiry can get stuck.
Imagine a customer trying to reserve an instrument repair at a Mississauga music shop. They can read the service description, but the mobile menu covers the request button when they enlarge the text. Another customer reaches the form and sees a red border after pressing Send. Neither can tell what to do next.
Give your designer one job to test from beginning to end. For this shop, the job is to find repairs, choose a service, submit contact details and read the confirmation. Set aside a phone, a laptop and a test inbox before approving the design.
Walk through the menu without a mouse
Start at the top of the homepage. Press Tab repeatedly and watch which item takes focus. You should see the current link or button every time. When you reach the menu control, open it with the keyboard, reach the repairs link and follow it. Use Shift and Tab together to move back through the same controls.
Repeat the test with the menu open on a narrow screen. If it opens as a modal dialog, close it with Escape and check that focus returns to the menu button. A sticky header should leave the focused item visible. Record the control where focus disappears or stops moving.
Check whether labels survive typing
A visible label should tell the customer what belongs in each field even after they type. For the shop, “Instrument type” and “Describe the repair” explain two different decisions. Use examples such as “Loose tuning peg” as optional help beside the relevant field.
Ask the designer to associate each label with its control in the code. On a phone, tapping the label for a checkbox should also toggle the box. Identify required fields in words. If email is the only way the shop replies, say so next to the email field.
Make a mistake on purpose
In the test form, leave out the email address and fill in everything else. Submit it. You want a message naming the problem and an easy route back to the field. “Enter an email address so we can reply about your repair” gives the customer a clear correction. Keep what they already typed.
Correct the email and submit to the test inbox. Confirm that the success message is readable and that the request reaches the shop. Ask someone using their usual screen reader to try both outcomes when possible. Record whether they hear the error and success messages when they appear.
Try the same task with larger text
- Increase the text size and try a narrow portrait screen. Read each field label and button without having to pan sideways across routine form content.
- Open the on-screen keyboard and enter the last field. Check that the consent control and submission button remain reachable by scrolling.
- Write down the device, page and exact failing step. A report such as “At enlarged text size, the sticky footer covers Send” gives the designer a repeatable fix.
Get the Done48 website launch checklist