How to use the UX Microcopy Generator.
Microcopy should explain the action or state at the moment of use. Preserve the distinction between saving a draft and publishing it.
Make the workflow fit your task.
Identify the user's current state and the exact effect of the control or message. Write the shortest wording that makes the action and consequence clear, preserving distinctions such as saving privately and publishing publicly.
- What you provide
- Interface state and user action.
- What you get
- Clear labels, hints and confirmations.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A button stores changes privately without making them public.
Completed example
Label the action Save draft, with supporting text explaining that publication is a separate step.
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 every button use a short generic verb?
Specificity matters when actions differ. Save draft communicates a different effect from Publish even though both store content.
Why does the label cause users to expect the wrong outcome?
Compare the wording with the actual state change. Add the missing object or consequence rather than relying on nearby explanation alone.
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 ↑