Tag Info

Hot answers tagged

7

You asked for an example of an implementation: Wordpress warns the user when it's likely they misspelled their email address. Like you said, this does feel like an error and not a 'soft error'. I agree with @Franchesca that you can use this, but should go for a less threatening color than red. But I wouldn't go for blue. I think orange is a better ...


5

This is known as "microcopy" in the UX world. A couple of good resources include http://www.smashingmagazine.com/2013/06/17/five-ways-prevent-bad-microcopy/ Nielsen-Norman group has a number of articles and training conferences on writing for the web: http://www.nngroup.com/topic/writing-web/ One of the big problems with form fields and validation, ...


4

I don't see anything wrong with this in principle. Anything that helps the user avoid mistakes is good. If you avoid all the trappings of error messages, such as exclamation marks and red writing then this could work. Perhaps use a question mark and a more neutral colour (blue?). Just make sure that the validation you are using doesn't have too many false ...


3

In order to spur users to action, I would put the solution directly in their face. Tell them about heartbleed (in a calm manner) and offer them the option to change the password immediately. Why ask them to navigate all the way to wherever they can reset their password when you can bring the form to them. Wait for them to log in, and give them a simple ...


3

You need to find a general tone that is appropriate given your users and the level of risk you want to protect them from. The right tone will be the one that your users find appropriate. They might resent your not warning them enough if one of their actions results in a big loss for instance and they feel they would have proceeded differently, had they been ...


2

You answered your own question! :) I think you should allow users to sign up without JavaScript. Users want an easy experience, they don't want to follow steps like how to enable JavaScript - they just want to sign up, do want they need to do and they're done. It's simply too much work to enable JavaScript. So I think the solution you gave in your answer ...


2

I see two options: Obfuscation, for example on Windows if you want to be able to mess with System Files you first need to know how to get a few menus deep and uncheck the box. (Which then also has a pop up almost identical to the one in your post.) A reset button, if it is possible for you to include a 'Reset to Default' then you could write a test that ...


2

We took the transparent approach and posted a notification inside our application for all administrators - we told them we WERE running the affected version of OpenSSL, we told them what we did, when we did it and why. We also told them there is no indication of anything untoward but due to the nature of Heartbleed this is expected though we did still spend ...


2

It's simple really. They are all alerts, dialogs, modals, etc. Warning is the type of the alert along with Error, Information, and many more.


1

As a general rule, you should avoid presenting users with lots of fields at once (all on one screen). It is daunting for a user to be faced with this (unless they are a call centre data entry employee or similar). You need to break the form up into small, manageable tasks that are presented in a logical order. When you break up the form there will be less ...


1

Just make them clear. Like "Please enter a phone number" for a missing required. Or "Please enter a valid phone number. The phone number you have entered is too short." Tell the user exactly what is required. It is also best to validate before submission with JavaScript and give them instant feedback. Show the error message right near the input field, and ...


1

If you should warn users is determined by your moral disposition on the subject and if it will work has too many variables such as the wording of the warning, the design and the frequency. As far as research, the most applicable would be split testing your users, in their environment with the definition of excessive use in relation to the users. With that ...


1

What level of security required is not a UX question. Rather it is a threat modelling exercise that will tell you how much you should demand the user changes their password. Once you have determined the degree of risk then what do you want to drive? A rational decision based on the risks. Users can do that providing they are not confused. Examples below ...



Only top voted, non community-wiki answers of a minimum length are eligible