Form Guide

1. Keep Forms Short and Simple
A user-friendly form is one that's simple and to the point. Avoid overwhelming users with too much information. If the form is too complex, consider using the progressive disclosure pattern. This design strategy involves breaking up the information into smaller, manageable chunks and only displaying them when necessary, thus keeping the user's cognitive load to a minimum.

Ref to 816:1727

 

2. Ensure Proper Tab Navigation for Accessibility
Ensure users can navigate through your form using only their keyboard is essential for accessibility. The tab order should intuitively follow the visual sequence of the form, allowing a smooth and logical navigation experience, especially for users who rely on keyboard-only interactions.

Ref to 816:1761

 

3. Provide Single Column Layout
Single column layouts are easier to navigate and reduce the chances of users missing out on filling important fields. They streamline the flow of information, making it easier for users to understand and complete the form.

Ref to 816:1938

 

4. Highlight Optional Fields, Not Required Ones
Marking optional fields as "(optional)" instead of highlighting required ones makes the user less think and the form looks less forbidding. This approach assumes all fields are required unless stated otherwise, making it easier to use.

Ref to 816:4318

 

5. Use Descriptive Labels and Helpful Error Messages
Descriptive labels help users understand what is expected in each field. In the event of an error, helpful and specific error messages guide users to correct the issue. Avoid technical jargon and keep the language simple and user-friendly.

Ref to 816:19900

 

6. Offer Real-time Validation
Real-time validation provides immediate feedback as users fill out the form. This helps users correct errors as they go, rather than after they attempt to submit the form. It reduces the chances of submission errors and improves the overall user experience.

Ref to 816:20033

 

7. Show Inline Error Messages After Clicking Submit
While real-time validation helps users correct mistakes during form completion, inline error messages displayed after form submission serve as an additional safety net. They provide immediate feedback if any errors were overlooked during the initial input, further assisting users in identifying and improving their mistakes. This dual-layered approach ensures a smooth and efficient form-filling process.

Ref to 816:20073

 

8. Limit Placeholder Usage
Placeholder text can be confusing or misleading if not used properly. It's best to use it sparingly, and only to indicate the expected format of input, such as for dates or phone numbers.

Ref to 816:20593

 

9. Use Single Text Field for Birthday
A single text field with a placeholder showing the expected format is a user-friendly way to ask for birthday information. It's simpler, faster and more accessible than using select dropdowns or date pickers.

Ref to 816:20701

 

10. Avoid Using 'Reset' and 'Clear' Buttons
'Reset' and 'Clear' buttons can cause users to lose their input accidentally, leading to frustration. It's better to avoid these buttons as most users expect their input to be preserved.

Ref to 816:22710

 

11. Show Loading Feedback and disable form
If the form needs to load after the CTA click, show a loading animation on the button and disable all form elements. This provides visual feedback and prevents users from making changes while the form is processing, thus avoiding potential errors or confusion.

Ref to 816:22972

 

MDX Form Elements