The first conversation happens before the reply
An enquiry form sets expectations while someone is deciding whether to contact a practice. A vague field, an unexplained error or an uncertain confirmation can make an otherwise welcoming website difficult to use.
Begin with the purpose of the form. Is it a general enquiry, a request for an appointment or a confirmed booking? The heading, button and final message should all describe the same action.
Keep the questions visible
W3C’s guidance on labelling form controls explains that labels identify a field’s purpose and need a proper association with the control. Visible labels also give people a reference while they type.
A practical example is a field labelled ‘Email address’, with any explanation placed beside it. Placeholder text inside an empty box should not carry the whole instruction: it can disappear as soon as the field is used. A form should remain understandable when it is partly completed.
Ask a question the reader can answer
‘Briefly tell us what you need help with’ is a more usable invitation than a large box labelled only ‘Details’. If the team only needs enough information to route an enquiry, say so and avoid encouraging a complete personal history in that first message.
Each required field should have an operational reason. An optional contact preference may be helpful; a mandatory field that staff do not use only adds another obstacle. The practice should decide the minimum information appropriate to its own workflow.
Make mistakes recoverable
W3C’s form-notification guidance addresses useful feedback, including identifying errors and helping people correct them. An error needs to be available to people who cannot rely on colour alone.
For example, ‘Enter an email address in the format name@example.com’ gives a next step. ‘Invalid input’ leaves the reader to guess. Keep correctly entered information in place where possible, and make it clear which question needs attention.
Finish the conversation clearly
A confirmation should name what was received and what happens next. For an enquiry rather than an instant booking, a sample message might read: ‘We have received your appointment enquiry. Our team will contact you to discuss a time. Your appointment is not yet confirmed.’ Any response-time promise should match what the team can reliably provide.
Review the complete journey with a keyboard, on a small screen and with enlarged text, including an intentional error and the final confirmation. These checks can reveal obvious problems; they are part of an accessibility review rather than proof of complete conformance. The examples here are editorial illustrations, informed by W3C guidance checked in September 2026.
