A contact form is often the last step between a visitor and a useful conversation. If its fields are unclear or an error is hard to find, a visitor may leave without knowing whether the enquiry was sent. An accessible form starts with understandable questions and a reliable reply route.
The W3C Web Accessibility Initiative forms tutorial covers labels, instructions, validation and feedback. The checks below turn that guidance into a brief that a business owner and web team can test together. They are a starting point, not an accessibility certification.
Ask only for information needed to reply
Decide which details are essential for the first conversation. A name, reply address and short description may be enough; sector, budget or project scope can often wait. Explain why any unusual field is needed. Avoid asking people to put passwords or sensitive documents into an ordinary enquiry form.
Make required fields clear in the label and provide examples for formats that could be misunderstood. The W3C advises giving instructions before or beside the relevant controls, rather than relying on placeholder text that disappears when a person starts typing.
Give every field a useful label
“Email address” tells a visitor more than “Details”. A visible label should stay available after the field contains text, and the code should associate the label with its control. The W3C labelling guidance explains why this helps screen-reader and speech-input users as well as people clicking on a label.
Check the order in which a keyboard user reaches the fields, choices, privacy link and submit button. A custom dropdown or date picker should not trap someone or require a mouse. Try the form at mobile width and with larger text, too; a tidy desktop layout is not enough.
Help people recover from mistakes
Test a blank required field, an invalid email address and a message that is too long. The form should identify the problem in words, near the relevant field, and tell the visitor how to correct it. Colour alone is not enough. W3C’s validation guidance recommends clear required-field information and accessible feedback.
After a successful submission, show an unmistakable confirmation. Send the enquiry to a monitored destination and define who replies. If the form fails, give the visitor another contact method. A polished confirmation screen cannot compensate for a message that never reaches the business.
A five-minute acceptance test
- Complete the form using only a keyboard.
- Leave one required field empty and check whether the correction is obvious.
- Use a phone-sized screen and enlarge the text.
- Send a real test enquiry and confirm delivery to the intended mailbox.
- Ask someone unfamiliar with the site to explain what will happen after they press Send.
Keep the test results with the website handover so later design or plugin changes can be checked against the same journey. If you are briefing a new website, include these requirements alongside content, privacy wording and ownership of replies. Our website quote comparison guide helps you check that testing and support are included in the scope. For help designing the full journey, see Kilwhiss Online web design or get in touch.