Open silviatc opened 8 years ago
From design meeting:
Notes for design break-out session:
Literally including the phrase “optional” after a label is much clearer than any visual symbol you could use (eg. an asterisk) to mean the same thing. Also, when you mark a form’s required fields, it jeopardizes voluntary over-disclosure and makes users skip optional fields. (source 1) (source 2)
Action items: pick a client side and server side form validation library (see here)
@silviatc FYI, mailcheck JS seems a little bloated from looking at the code. If we end up wanting to implement a JS checking solution, we might just want to see what domains we support and lump it in with any existing regex checking we do against email addresses. I would be happy to help with the implementation as needed.
@hardboiled wonderful! We're meeting today about validation so for now, I'll edit my comment with your fix and update as needed. We're meeting at 5 at Center Stage if you'd like to join... always helpful to get a developer in the room.
From design breakout session with @GeorgeTaveras1231 @rutu9 @jameree @leetaniau: The goal was to create a system for alerts and notifications, and use that to build out documentation for form validation.
Style | Example | Trigger |
---|---|---|
Inline |
|
|
Toast |
|
|
Block |
|
|
Modal | ||
Tooltip | ||
Overlay |
Literally including the phrase “optional” after a label is much clearer than any visual symbol you could use (eg. an asterisk) to mean the same thing. Also, when you mark a form’s required fields, it jeopardizes voluntary over-disclosure and makes users skip optional fields. (source 1) (source 2)
Required field validation needs UT.
Possible solutions:
Research: http://uxmovement.com/forms/always-mark-optional-form-fields-not-required-ones/ http://www.lukew.com/ff/entry.asp?725 http://ux.stackexchange.com/questions/73728/should-form-continue-button-be-disabled-if-validation-is-incomplete https://css-tricks.com/form-validation-ux-html-css/