Anecdotal: Yes. My experience is that people are far less resistant to voluntary surveys after signup/account creation. If you need to have this information before first use of the product/service, it should still be presented as a survey after the account has been created. In either case, you should preface the survey (or the request that the user take the ...
The best option would be to go with the single password field, but ONLY if these are both applicable:
Your "forgot password" functionality is a smooth process. It should be a quick and easy process that makes resetting the password can happen effortlessly.
You give the user the option, with a checkbox or something, to make the password entry ...
I think what you have in the second "dropdown" comp is a pretty good start. I would adjust the field sets a little bit to improve the overall experience. In doing some research, I discovered how some custom web design tools handle their container layout fields. One in particular was WebFlow. Their Sizing tools are pretty intuitive. First they set ...
This solved probably the best way in popular taxi and food delivery applications, which frequently imply such an option.
The control can be a link or a button instead of a calendar image. Especially in this case, when the actual time cannot be picked, e.g.:
Once pressed, a radio-button selection can be shown, e.g.:
Without the option to select the actual ...
Assuming you need a UX solution rather than a technical one, if the character count can't be accurate then don't use one. Try an alternative pattern, such as a completion 'progress bar' that fills up as the user types.
Once they get over the maximum limit then let them know so they can amend it.
Using a mouse click somewhere dead on the page, such as in between interactive elements, will achieve the removal of focus (blur) from whatever element had it..."
Well, kind of.
As you know, Tab just moves focus through the focusable elements in the document, stepping through each focusable child of each HTML element.
However, the browser ...
DO NOT skip form fields or prevent keyboard nav to interactive elements. Always refer to WCAG for interactive elements.
DO apply smart autofill so people don't have to key in the same info multiple times. That's just good usability for everyone, including keyboard navigators. :)
I don't know if there's a way to do it, but the answer is that you should not terminate navigation unless you have some kind of reason for doing so for ALL users (mouse, touchscreen, keyboard, etc.)
Keyboard is another form of navigation and control, just like mouse and touch. The rule of accessibility is that whatever you can access or control by mouse/...
Yes they should be able to.
Most confirmation emails, much like rest password email, are valid for 24 hours.
If you don't confirm it then your account is not verified.
"Then, some guy registers using that same email." After 24 hours that email has become available again.
Keep people at the center of data collection. People easily relate to a 10 point scale. For example, all TV reality shows have a rating scale of 10. People subconsciously relate to brands using a 10 point scale. Although the conversation is open for debate, I have seen 10 point scales work best for research studies I have done in past.
Below are some screen ...
I would make it a 2-step form: first username + password, then full name & e-mail ('To get to know you!').
This resource might also be of help: https://www.nngroup.com/articles/checklist-registration-login/
Personal opinion, but I agree that Other or Custom is preferable to 100+.
This may be a case where you can keep the default ranges and use something like a range slider for your custom input.
Here the user clicks/presses on the 1 - 25 range, then on the Other button which animates a change in the control. The range box on the left could accept keyboard input ...
I think I would go for a side panel, something like the Wordpress Plugin Forminator (https://wordpress.org/plugins/forminator/):
See https://blog.hubspot.com/marketing/form-builder-tools for some other ideas.
I've came to a point when the tag input had more than 1k items, and sending the input value to the backend started to give "414 Request URI too long" errors. I will now switch the tags to stay outside the input to send only the changes to the backend. The delete button will remain to delete the tags, and adding new tags will clear the input. (Until ...