How to use the Web Form Required Field Explainer.
Explain required fields using the form's actual labels and help text. Do not invent why an organization collects a sensitive field.
Make the workflow fit your task.
List fields actually marked required and preserve their labels, help text and format rules. Explain how to prepare each value using only supplied guidance. Note conditional requirements and distinguish a missing explanation from an inferred reason for collecting information.
- What you provide
- Visible form and its help text.
- What you get
- Required information checklist with field-purpose explanations.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Form visibly requires company name, work email and invoice reference. No additional format guidance supplied.
Completed example
Required information: - Company name - Work email - Invoice reference Format rules: not supplied beyond the field labels. Prepare these values and inspect any help text or validation messages before submission; no reason for collecting additional sensitive information is assumed.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should optional fields be included in the required-information checklist?
Keep them separate, unless a visible condition makes them mandatory for the selected path through the form.
Why does a new required field appear after choosing an option?
The form may use conditional sections. Review the selected path and update the checklist to match the visible state.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑