Quick Answer
Specify an inquiry form by writing what triggers each message, what the visitor can do next and what evidence confirms the underlying result. Separate a browser’s displayed confirmation from the application accepting a request, an email being delivered and a team member receiving it. Use this state worksheet before approving the form’s interface.
A “thank you” screen can look convincing while the inquiry goes nowhere. User interface design needs a precise agreement between the message shown to the visitor and the process behind it. The example below is a proposed specification for a service inquiry, not a report of a form we tested.
Define the request and its destination
Identify the fields the responsible team needs to assess the project. Name the application or system that stores the accepted inquiry and the notification route that alerts staff. Define who investigates a missing notification.
Write the intended meaning of “submitted” before designing that message. An application may accept a request while its notification is delayed. Conversely, a browser may show an error after the application has accepted it. The implementation needs a way to investigate those cases without encouraging repeated submissions blindly.
Use a worked feedback and evidence worksheet
Adapt these example messages to the actual system. Do not display a status or reference number unless the implementation can support it.
State and trigger
- Required project description is missing
-
Visitor message and next action
“Add a short project description.” Identify the field and let the visitor correct it without losing other input.Evidence to check separately
The missing value is identified accessibly and no complete request is accepted. - Submission is being processed
-
Visitor message and next action
“Sending your request.” Explain the pending state and prevent accidental repeated activation appropriately.Evidence to check separately
Check the actual request and response, including a delayed connection. - Application accepts the inquiry
-
Visitor message and next action
“Your request has been received.” Explain the next step using the business’s approved response process.Evidence to check separately
Confirm the accepted record contains the expected test details. Check notification delivery and team receipt as separate outcomes. - Submission fails or the outcome is uncertain
-
Visitor message and next action
Explain what is known and provide an approved recovery or contact route. Avoid falsely confirming receipt.Evidence to check separately
Inspect the application result and logs before deciding whether a retry could create a duplicate.
Connect each message to the relevant control
Keep field labels visible during entry and associate them with their controls. W3C’s form labeling guidance explains that association. Make an error identify what needs correction, instead of changing only the field’s color.
Check the correction and submission process with a keyboard and on a narrow screen. The WCAG keyboard criterion addresses keyboard operation, with its underlying path-dependent input exception. One form check does not establish complete accessibility conformance.
Turn the worksheet into an acceptance record
For each row, record the environment, test details, observed message and underlying result. Use authorized test information. Have the intended recipient confirm receipt when that is part of the requirement. Keep sensitive logs and credentials out of the public report.
When a case fails, record which step failed rather than marking the whole task “working” because a screen appeared. Review the corrected case and any affected notification route. Put these acceptance conditions into the website design brief and assign recurring delivery checks through the agreed website care responsibilities.
Key Takeaways
- Define the actual meaning of an accepted inquiry.
- Specify a trigger, message, next action and evidence for each state.
- Verify application acceptance, notification delivery and team receipt separately.
- Keep an acceptance record that identifies the environment and observed result.
Frequently Asked Questions
Does a thank-you message prove an email arrived?
No. Verify the application’s accepted request, the notification’s delivery and the recipient’s receipt separately. The browser message should accurately reflect the result the application knows.
Should an uncertain submission always be retried?
First check whether the application accepted it. A connection problem can leave the browser uncertain even when a record exists. Define recovery and duplicate handling for the actual implementation.
Who approves the follow-up promise?
The responsible business team needs to approve the response process and any timeframe shown. A designer should not invent a response commitment to fill a confirmation screen.

