On a desktop, a seven-field enquiry form can look pleasantly compact. On a phone, the same form arrives with a keyboard covering half the screen, a connection that occasionally pauses and a visitor trying to remember which information you asked for.
To review a form properly, fill it in on a real phone. Use one hand. Make a mistake. Switch to another app to copy a detail, then return. The awkward moments you notice are often more revealing than a screenshot.
Earn each question
Ask what your team will do with every answer. A name, email address and short description may be enough to begin a conversation. A detailed company profile, exact budget and full postal address might belong later.
There are good reasons to qualify an enquiry, but the questions should match the stage of the relationship. If a budget range helps route the request, explain why and offer useful ranges. If a phone number is optional, say so rather than leaving visitors to guess.
Keep labels visible
A placeholder can show an example, but it disappears when someone types. A persistent label helps the person remember what belongs in the field. W3C's form guidance describes how labels should be associated with their controls, including for people using assistive technology.
Consider the wording as carefully as the layout. “Tell us what you need help with” is often easier to answer than “Project requirements.” Where a format matters, show a short example before an error becomes necessary.
Make errors repairable
“Invalid input” does not explain how to fix a problem. “Enter an email address such as name@example.com” gives the visitor something to do. Put the message near the relevant field and preserve the answers that were already valid.
A failed network request needs a different message from an invalid email address. If submission fails, keep the entered information and provide a retry path. Do not clear the form and make someone reconstruct a paragraph they just wrote.
Finish the conversation after submission
A button changing color is not a confirmation. Tell the visitor that the enquiry was received, explain the next step and give a realistic response expectation your team can maintain. Where useful, show a reference number or a way to add information.
Make the sending state visible as well. Disable repeat submission while the request is in progress, and ensure the system handles accidental retries without creating unnecessary duplicate work.
- Check that every field has a visible, associated label.
- Try the form with a keyboard and with a phone.
- Submit incomplete information and review every error.
- Simulate a failed request and verify that answers remain.
- Read the confirmation as a customer who has never contacted you.
Further reading: W3C WAI guidance on labeling form controls.



