Websites & support / Checklist
Make your enquiry form easier to finish
A contact form can send its emails correctly and still be awkward to use. Somebody might get stuck on a required field, lose a long description after an error or struggle to work out what the form wants from them.
I want to try the form as a customer before declaring it finished. That includes making an ordinary mistake and seeing whether the page helps me put it right.
Ask what you need for the first conversation
Look at every question and ask what happens to its answer. If a field is needed to route the enquiry or arrange a response, give it a clear place. Information that can wait for a conversation may not belong in the first form.
For an invented callback form, the business might need a name, a number and a short explanation of the request. The exact questions depend on how that business follows up. A quote for building work may need different context from a request to discuss a website.
W3C’s form guidance recommends asking only for information required by the process. Use that as a reason to examine each field, rather than copy another company’s form.
Source: W3C WAI: forms tutorial
Keep the field names visible
Give each input a label that remains understandable when someone starts typing. A prompt shown inside an empty box can disappear just when the person needs to check what they are entering.
Make required questions clear in text. If there is a special instruction, put it beside the relevant field before someone encounters an error.
Ask the builder to check that labels and instructions are correctly associated with the controls. The visible layout and the information available to assistive technology both matter.
Source: W3C WAI: forms tutorial
Accept the way people normally enter their details
Try a phone number with spaces and one without. Check whether the form accepts reasonable formats for the countries you serve. A customer should understand any format the business actually requires.
W3C’s validation guidance describes accepting ordinary variations in input. It also explains that the server needs to validate the data, even when the browser has already checked it.
In the callback example, entering a spaced number should leave someone able to continue. If the value genuinely needs correcting, explain what to change at that field.
Source: W3C WAI: validating input
Let someone fix one mistake and carry on
Use fictional details in a test copy of the form and deliberately leave a required answer empty. Check that the page identifies the question and keeps the other useful text already entered.
An error message should help the visitor correct the problem. Please enter your name gives somebody a specific next step. A general failure message leaves them guessing which part needs attention.
Check the route to that message with a keyboard and with the accessibility tools appropriate to the site. Also test the smaller screen: the error and its field need to be easy to find without hunting around the page.
| Try in the test form | Look for |
|---|---|
| Leave one required answer empty | A specific message and the other entered details retained |
| Enter an ordinary spaced phone number | A reasonable value accepted or a useful explanation |
| Move through with the keyboard | A visible focus position and a sensible order |
| Complete the agreed test submission | A clear result and an understandable next step |
Explain what happens after the form
The final message needs to match the result the system actually received. Tell the visitor whether their enquiry was accepted and what the agreed next step is. Keep response promises tied to what the business can deliver.
Then check the separate delivery journey. A form that is easy to finish still needs its enquiry to reach the right place; our missing-form-email article follows that part of the process.
Bring a real enquiry task to the website brief, with fictional details for testing. It gives us something more useful to judge than whether the empty form looks tidy.
Sources
Checked on 23 October 2026.
- W3C WAI: forms tutorial
Necessary questions, associated labels and instructions, and understandable completion and error feedback.
- W3C WAI: validating input
Forgiving ordinary input formats, accessible validation feedback and server validation alongside browser checks.