Ask only what the first contact needs
A first enquiry form should help arrange a conversation. Start with a name, a reliable contact method and a short description of the request where necessary. Explain which fields are optional. Avoid turning the first contact into a long intake questionnaire. A visitor may be using a small screen, an assistive tool or simply have limited time. Decide what you can ask later during an appropriate intake process, and remove fields that do not help you respond.
Keep field labels visible
A placeholder disappears as soon as someone types. Use a visible label for each field and associate it with the control so assistive technology can identify it. W3C guidance recommends descriptive form labels and keeping the relationship between a label and its field clear. Use appropriate input types, such as email, so mobile devices can offer a suitable keyboard. Group related choices logically and explain unfamiliar terms before asking someone to select an answer.
Make mistakes easy to correct
If an email address is incomplete, explain the problem next to the field. Do not rely on colour alone to identify an error. Preserve the information already entered so the visitor does not have to start again. Check that the form can be completed using a keyboard, that focus is visible and that the submit button describes the action. These practical checks are useful starting points; they are not a substitute for a full accessibility assessment.
Be precise about what happened
After submission, distinguish an enquiry from a confirmed appointment. If the form opens an email app or WhatsApp, tell the visitor that they still need to press Send there. If a server receives the enquiry, show success only after it confirms receipt and provide a useful error message if delivery fails. Test with fictional details on a phone and computer. Ask a colleague to complete the process without instructions and watch for points of uncertainty. A calm visual design matters most when the underlying interaction is dependable.