
A contact form can look polished and still be difficult to use. A visitor might reach the page but lose track of which field is selected, become stuck inside a popup, or receive an error message that does not explain how to continue. Those problems happen before an enquiry reaches the mailbox, so an email-delivery test will not uncover them.
A keyboard review gives a small business a practical way to find some of these obstacles. It is a first check, not an accessibility certification or a substitute for testing with assistive technologies and people with disabilities. The aim is to turn a vague concern about the form into a clear description that a website maintainer can investigate.
Pick a realistic task, such as asking for a quote from a service page. Start where a customer would start, rather than opening the contact form directly. Include the navigation, enquiry button, any popup and the final confirmation screen.
Write down the starting address, browser, device and date. Use test information rather than a real customer’s personal details. If submitting the form will create a lead, trigger an SMS or enter a booking system, agree the test with the person who receives those records first. Mark the submission clearly so staff do not mistake it for a genuine enquiry.
W3C’s Easy Checks explain the value and limits of an initial review. Passing a short set of checks does not prove that a website has no accessibility barriers. Keep that distinction in the test record and in any claims made about the result.
Use the keyboard to move through the page. Tab commonly moves between interactive controls, while Shift and Tab move backwards. Exact behaviour can depend on the browser and operating-system settings, so note the environment if something behaves unexpectedly.
Watch for the indicator showing which link, button or field currently has focus. W3C’s explanation of visible keyboard focus describes why this matters: people need to know which control will respond to their next action.
For your own test, note where the indicator first becomes difficult to see. Is it hidden against a similar background, covered by a sticky banner, or missing on a particular button? Record the control’s label and a screenshot where useful. “Cannot see focus on Request a Quote” is a more actionable finding than “the contact page feels broken”.
Many business websites put their enquiry form inside a popup. Test opening it using the keyboard, moving through its fields and closing it again. Include cookie notices, chat panels or other components that may appear over the same page.
W3C’s no-keyboard-trap guidance explains that a user who can move focus into a component must also be able to move away using the keyboard. If an unusual exit method is necessary, users need instructions.
If you become stuck, do not hide the problem by clicking the background and continuing. Record the point of failure and the keys tried. A developer needs to distinguish a genuine trap from a missing instruction, a browser setting or a component that is behaving differently from expected. Test the same journey again after the issue is corrected.
Typing into the name field is only part of the journey. Check service selectors, checkboxes, date fields, file-upload controls and the submit button. Some controls use arrow keys or other conventional keyboard interactions, so the test should consider the kind of control rather than expecting every action to use the same key.
The W3C keyboard guidance describes the principle that functionality should be available through a keyboard interface, with a limited exception for functions that inherently depend on a movement path. An ordinary enquiry form should not require a mouse just to choose a service or submit a request.
Prepare a small task list before testing. For example: choose a service, change that choice, add a message, attach a harmless test file if needed, and submit. This avoids checking only the easiest route while overlooking a control that customers actually need.
A field may look understandable when it is empty because it contains placeholder text. Once someone types, that hint can disappear. Check whether the purpose of each field remains clear, including any required format or instruction.
W3C’s form-label tutorial explains how labels identify controls and how they should be associated in the underlying markup. A visual review cannot establish every part of that association. Ask the maintainer to inspect the implementation if a field appears to rely only on placeholder text or an unexplained icon.
Record ambiguities in customer language. A field labelled “Reference” might mean an existing job number, a property address or a preferred contact. Improving that wording can help everyone, but the business should decide what information it actually needs before a developer changes the form.
With permission to test, try leaving a required field empty or entering an obviously invalid test email address. Avoid repeatedly submitting the form or using sensitive information. The purpose is to understand the error path, not to generate unnecessary records.
W3C’s form-notification guidance recommends clear feedback about success and errors, including information that helps people resolve a problem. Check whether you can identify which field needs attention, understand what to change and return to it without starting over.
After correcting the test entry, complete the submission and inspect the confirmation. A generic colour change or disappearing button may leave a customer unsure what happened. Record what the page actually says. If the confirmation claims a response time, ask the business owner to verify that promise rather than introducing a new commitment during a technical fix.
A successful on-screen submission does not by itself prove the business received an email, a CRM record or an attachment. Treat those as separate checks, with a clear link between the test submission and the received record.
Our guide to missing enquiries when a form says sent covers the delivery side. For this keyboard review, keep the finding precise: the visitor could or could not complete the form, and the business did or did not receive the identified test. Combining those statements into a single “form works” result hides useful information.
If the form contains payment or booking actions, use an agreed test arrangement. Do not create a real charge, reserve stock or book an appointment merely to test navigation.
For each issue, record the page address, starting point, steps taken, expected behaviour and observed behaviour. Include browser and device details, relevant screenshots and the test time. Avoid including passwords, payment details or unnecessary personal information in the report.
Prioritise barriers that prevent completion, then problems that cause confusion or make the journey unnecessarily difficult. Ask for a specific correction and a retest of the same route. A broad request to “make everything accessible” can obscure an immediate, reproducible fault, while a narrow fix should not be presented as a full accessibility assessment.
Tempwebz can discuss website edits and maintenance or help investigate a specific issue through technical support. Send the test record with your request. The useful outcome is a customer journey that has been checked again after the change, with remaining limitations clearly recorded, rather than a checkbox marked complete because a plugin was installed.