Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

write up blog post on what we're doing around help text and help forms #52

Open
jdkunesh opened this issue Dec 17, 2019 · 3 comments
Open
Assignees
Labels
design documentation Improvements or additions to documentation

Comments

@jdkunesh
Copy link
Contributor

See #46

We should publish details of this work & the research we have done to share with vendors and departments the reasons behind the work we are doing.

@jdkunesh jdkunesh added documentation Improvements or additions to documentation design labels Dec 17, 2019
@jdkunesh jdkunesh added this to the Sprint 3 - component mania milestone Dec 17, 2019
@alaeder16
Copy link
Collaborator

Form Design Best Practices: Tips to improve UX
Web forms — where your site visitors can input and submit their information. Great form design enhances UX and helps boost conversions.

  1. Use one column. Single-column layouts are easier to follow, understand, complete, and submit for your visitors. A study by CXL Institute found participants were able to complete a single-column form an average of 15.4 seconds faster than a multi-column form.

  2. Arrange your form fields from easiest to hardest. Start your form with the easiest field questions (like name and email) before asking your visitors the more time-consuming questions

  3. Align text to the left. University of Basel researchers found aligning your text on the left side, above the form field box, lowers the amount of time needed to complete the form. This natural alignment decreases the amount a user’s eyes need to jump across the page and makes the form more readable.

  4. Use Input Constraints for Form Fields. Input constraints place a limit on the number of words or characters a person can type into your form field.

  5. Address possible user concerns with summary boxes or help tips. You can address concerns with summary boxes explaining your need for certain information or with statements that clarify whether or not the form field is optional.

  6. Use UI Patterns for common information blocks. UI patterns are repetitive solutions to common, recurring design-related problems your visitors face while completing your forms. These solutions work over and over again to improve your form’s UI and ease of use.

@jdkunesh
Copy link
Contributor Author

jdkunesh commented Feb 3, 2020

@alaeder16

I added this to https://github.com/Chicago/design.chicago.gov/tree/master/_posts

However, I had some questions about the content.

  • Explain which of the standards you've listed are created vs found. For those you found, add sources.
  • Give the reader some context on what these best practices are
  • Highlight how the CDS makes following these best practices easier.

@alaeder16
Copy link
Collaborator

Forms is the one of the most important type of interaction for users on the web and in the apps. They are used everywhere — for registration, subscription services, customer feedback, checkout, to initiate transactions between users and companies, or as data input to search or share information. Using best practices guidelines CDS helps improving their forms and making them as usable as possible, because careful form design has a huge impact on the speed with which users can accurately complete a form. Below is an outline of some important practical recommendations that should be used as a starting point for form design.

At the end we can add references to:
hubspot.com - Form Designs Best Practices
UX Planet - 10 rules for Efficient form design
U.S. Web Design Standards - Forms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants