This focused guide explains a practical task and the decisions that help make the result clear and useful. For related planning, continue with contact page guide accessibility checklist.
1. Define the form task
State what the form is for and who will receive the response. Ask only for details needed to complete that task; unnecessary fields add effort and may discourage people from continuing.
Decide what happens after submission, including who reviews the request and how the visitor will hear back. Do not imply a response time or process that the organization cannot meet.
2. Select fields and write instructions
Choose the appropriate input for each piece of information and group related questions. Use visible labels rather than relying on placeholder text that disappears when someone begins typing.
Explain required fields, accepted formats, and sensitive requests near the relevant control. Avoid asking for health, financial, or other sensitive details unless there is a suitable, approved process for handling them.
3. Arrange the form in Wio
Give the form a concise heading and a short explanation of what will happen next. Arrange questions in a logical sequence and keep supporting policy or privacy information easy to find.
Use Wio to compose the visual section, but confirm that a connected form service provides the required validation, submission handling, privacy controls, and confirmation behavior. A visual form layout alone does not process submissions.
4. Test the entire submission path
Try the form with typical, missing, and incorrectly formatted responses. Check field labels, error messages, keyboard use, mobile layout, and whether the success state is clear.
Confirm that a submission reaches the right destination and that personal information is handled as described. Link the form to a relevant contact page and review it whenever the process changes.
