How to use the Design Critique Generator.
Critique the design against a user goal and visible evidence. A screenshot cannot reveal every keyboard state, loading behavior or interaction.
Make the workflow fit your task.
Evaluate the supplied design against a stated user goal, citing visible evidence for each finding. Separate layout and wording observations from interaction behavior that cannot be established from a static image.
- What you provide
- Page content or supplied design image and user goal.
- What you get
- Evidence-based usability critique with uncertainty about unseen interactions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A checkout screenshot shows two equally prominent buttons with unclear labels.
Completed example
Clarify the primary action and button meanings; reserve judgment about keyboard behavior until it can be tested.
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.
Can a screenshot reveal whether keyboard interaction works?
No. It can show visible design choices, while focus behavior and control operation require an interactive review.
Why does the critique contain preferences rather than actionable findings?
Connect each observation to the user goal and a concrete consequence. Distinguish a usability concern from an optional stylistic choice.
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 ↑