Review one enquiry task from field labels to server confirmation, including invalid input and uncertain network outcomes.
A guest wants to ask whether a Sauraha guesthouse has space for a family. The form asks for several details, but its labels disappear when typing begins. After submission, a red border appears without explaining the problem. The guest cannot tell whether the message was sent.
An enquiry form should help people complete a task and understand the result. Clear labels, useful instructions and recoverable errors matter on a small screen, especially when someone is using a keyboard, assistive technology or an unreliable connection. This is a focused form-design review, not a plan for an entire business website.
For a hypothetical guesthouse enquiry, the initial task is to request availability, not complete a confirmed booking. The business might need an arrival date, departure date, guest count and a way to reply. Decide why each field is necessary before adding it.
Optional information should be marked clearly. Do not imply that sending the form reserves a room unless the actual booking process makes that commitment. Explain what the business will do next and provide a practical alternative contact route where appropriate.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
| Field |
Reason to collect at enquiry stage |
| Arrival and departure |
Describe the requested stay |
| Guest count |
Assess the requested capacity |
| Reply contact |
Allow the business to respond |
| Optional note |
Capture a relevant question without forcing extra detail |
Keep the label visible and associated with the field
W3C’s forms tutorial explains the role of labels, instructions, structure and feedback in making forms understandable. A placeholder can illustrate an expected value, but should not be the only label. Once someone types, the field must still communicate what it means.
Ask the developer to associate each visible label with its control and check that keyboard focus follows a sensible order. Required status should be communicated clearly rather than through colour alone. These are design and testing requirements, not a claim that a particular website is compliant with an accessibility standard.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. Conceptual interface. No actual guest information or live website screenshot.
The conceptual example uses persistent labels and an error next to the relevant field. It contains no real guest information and is not a screenshot of a live W3-built website. Its purpose is to make the intended interaction reviewable before implementation.
Explain errors without making the user start again
An error should identify the affected field and explain how to correct it. “Please check your arrival date” is useful only if the rule is also clear. If departure must follow arrival, show that relationship in ordinary language. Avoid a generic failure message that leaves someone guessing which entry is wrong.
Keep valid information when a correction is needed. A user who fixes one date should not have to type the whole message again. W3C’s validation and notification guidance is a practical reference for associating errors with fields and explaining outcomes; the exact implementation still needs testing.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Separate a click from a confirmed enquiry
The browser can react immediately when a button is pressed, but that is not the same as the server accepting the enquiry. Show a clear sending state and an honest outcome. If delivery is uncertain, explain it rather than displaying a success message merely because a click occurred.
In a hypothetical acceptance exercise, testers perform ten distinct scripted attempts. Six are accepted, two contain validation errors and two receive no confirmed result because the connection is interrupted. Ten equals six accepted plus four unresolved-or-correction outcomes under this example’s categories.
HYPOTHETICAL / ten scripted test attempts. Invented test categories, not conversion data or results from a real website.
Do not call the ten button presses ten customer enquiries. The exercise is invented and is not a measured conversion rate or evidence of a real website’s performance. A retry also needs a defined way to avoid recording the same intended enquiry twice; ask the implementer how it handles uncertain submissions.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
Test the task on the devices people actually use
Check the form on a narrow phone viewport, with the keyboard open and with longer text than the designer’s sample. Inspect whether controls remain visible, instructions wrap clearly and error feedback can be reached without losing context. Also test keyboard-only navigation on a computer.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
Use an agreed acceptance checklist: labels, required fields, valid submission, invalid submission, network interruption and confirmation. Record the expected result before testing. The example sequence below is a suggested review process, not a certification or a claim that automated checks replace human evaluation.
Suggested acceptance checks, not an accessibility certification.
After acceptance, someone inside the guesthouse must receive the request and know what to do with it. Check which contact details staff can access, who owns the reply and how a duplicate or mistaken submission is handled. Avoid sending personal form contents into analytics just to count an event.
A CRM connection may help assign the enquiry, but its actual integration must be verified. If considering WorkSphere, ask which accepted form event creates a record, what happens if the CRM is unavailable and how staff can trace the original request. The user-facing success message should match the business commitment.
W3C WAI Forms Tutorial
W3C WAI Form Validation
W3C WAI User Notifications