Website Design
By Website Design Company editorial team · Reviewed 2026-10-14
Ask only what you need
Keep the first enquiry short: contact name, reply email, service interest and a useful message. Additional qualification questions can come later. Avoid requesting sensitive account credentials or payment-card details in a general-purpose form.
Use visible, persistent labels
Place a visible label next to every input and connect it programmatically. Placeholders can provide examples, but they disappear while typing and should not be the only explanation. Indicate required fields before submission.
Explain errors where they happen
Validate on the server and show useful client-side feedback. Preserve input after a failure. An error should describe how to fix the issue without exposing technical details. Announce submission status to assistive technology.
Support keyboard and mobile use
Maintain a predictable focus order, visible focus indicators and sufficient tap targets. Use appropriate input types and autocomplete hints. Test at narrow widths and with browser zoom rather than assuming a responsive framework handles every state.
Treat delivery as a separate requirement
A form is complete only when a valid submission reaches the intended workflow. Persist the enquiry before attempting email notification. Track failures and provide a retry mechanism so a temporary mail outage does not silently lose a customer request.