Guidelines for Form Design
Click here to see a good example of form design
1) The path to completion should be clear
- Avoid multiple columns
- Left align labels and fields
- Use wizards to break long forms
- Indicate completion progress and if possible, allow users to save progress
-
Make primary and secondary call-to-action buttons distinct and obvious
- Call-to-action labels should be short and clear
-
Choose field types appropriately - this reduces confusion and makes data
collected easier to process
- Group related fields
-
Label fields as optional instead of compulsory
- Avoid using asterisks to mark compulsory fields
- Do not use placeholders to replace labels
- Use autocomplete
3) Feedback on interaction should be given
- Field validation should be inline (Display errors next to the field)
- Avoid using aggressive tone in error messages
- Validate inputs in real-time
This is an interactive demo for you to experiment with some general form elements.
Note: The hint text here is made visible intentionally for the purpose of demonstration.
It should not be visible in actual usage, unless necessary.
Code