Specify the workflow behind the form →
Define what happens after the enquiry is stored.
Business, marketing and professional work
A Mobile Friendly page can still fail when a form loses the message or a confirmation promises nothing specific. Test the whole customer task, including the awkward moments.
This fictional repair-business example shows the content and checks needed for a mobile web site enquiry.
A sample route for a bicycle-repair enquiry.
Opening: “Ask about a bicycle repair. Tell us the fault and when you need the bicycle back; we’ll confirm whether we can take the job.”
Fields: your name; email or preferred contact number; bicycle type; what is happening; preferred return date, labelled as a request rather than a guaranteed slot.
Before submit: “Please do not include payment-card details. Sending this enquiry does not reserve a workshop slot.”
Confirmation after successful storage: “Your enquiry has been received. Reference: DEMO-104. We’ll reply through your chosen contact method within the response period stated by the business.”
This is copy for a fictional service. A real page must replace the demonstration reference and response wording with its actual process.
A small screen is only one condition.
| Test | What should remain possible |
|---|---|
| Submit with a missing contact detail | Find the error beside the field and retain the rest of the message. |
| Receive a slow server response | Understand that submission is pending and avoid accidental duplicate requests. |
| Return after an interrupted connection | Know whether the request was received, with an appropriate retry path. |
| Use a keyboard or assistive technology | Reach labelled controls and understand the error and confirmation messages. |
| Zoom or increase text size | Read the request and complete the task without hidden controls. |
Business continuity includes the form destination.
For Free Mobile Website Design, establish who controls the domain, content and enquiry destination, and which ongoing charges or limits apply. “Free” does not explain the operating arrangement.
W3C’s forms tutorial covers labels, instructions and feedback. Use those principles alongside a real submission test: a polished form that sends nowhere has not completed the customer task.
After launch, test with an approved dummy enquiry and confirm its arrival and reply route. Record the test without retaining somebody else’s personal details as evidence.
Open the source for the part you want to examine further.
External reference · w3.org
The standards body’s tutorial covers labelling, instructions and feedback that help people complete forms.