Define what a successful test proves
Draw the actual contact route before clicking. A typical example passes from visitor to form, server, messaging service and receiving inbox. Other systems store enquiries in a work queue. Document the route in use rather than assuming what the service does.
Assign a check to each stage. A server can accept a request without an email reaching the correct person. An inbox can receive a message without anyone taking responsibility for it. Write a concrete completion condition: a marked test enquiry is visible to the designated recipient with the expected content. That demonstrates the outcome of this test, not guaranteed future delivery.
Prepare a safe test card
Use an address you control and a unique identifier such as TEST-FORM-07. Avoid real customer information, passwords and sensitive matters. Agree who knows about the test and how its data will be removed. A form that triggers bookings or external tasks requires an isolated environment or an explicitly approved test route.
Record the page, language, time, browser and intended recipient. The same component can use different settings in different languages. Cover at least one real contact route per configuration and every important variant. Testing the homepage does not establish that a separate quotation form has the right destination.
| Test | Expected observation |
|---|---|
| Required field left empty | Helpful feedback associated with the right field |
| Invalid address | The user can correct it without technical knowledge |
| Valid test enquiry | Truthful confirmation and verified receipt |
| Simulated delivery failure | No false success; an understandable next step |
| Keyboard operation | Fields, errors and outcome can be reached and understood |
Test recovery from an error
Leave a required field empty and try an invalid address. Can the person identify the field that needs attention and understand how to fix it? Continue using the keyboard. Check that focus does not disappear behind a dialog or become trapped in a component.
W3C WAI provides guidance on clear submission feedback and useful error messages. Use it to support the review rather than treating an automated result as proof of complete accessibility. Correct an error and submit again. An error marker that remains after the problem is fixed creates a different obstacle from the original validation.
Follow a valid enquiry to the intended recipient
Send the marked enquiry and record precisely what the page claims happened. Locate the same identifier in the receiving system. Compare subject, sender information, message and selected options. Check that the intended reply workflow works; displaying an address and providing a usable reply route are separate matters.
A confirmation must not describe an enquiry as a confirmed booking if no booking exists. If you can only verify acceptance into a queue, say so in the report. Without access to the final destination, the test is incomplete. A green status box or analytics click does not resolve that uncertainty.
Exercise the failure path without disturbing operations
In a test environment, the developer can substitute a controlled delivery failure. Verify that the interface does not report success and gives the visitor a sensible next step. Assess whether entered information is retained safely for correction or another attempt. Server internals, private addresses and secrets do not belong in an error message.
Finish with a short record: identifier, observed outcome, remaining uncertainty, owner and retest. Remove test data according to the plan. Repeat relevant checks after changes to recipients, delivery services or form settings. This protocol concerns the contact route; consent, retention and the organisation's handling of personal information require their own assessment.