I would like to advise you not to use Yes/No as radio buttons.
It is advised to use sentence style labels in imperative style.
Now, to answer the question in which order the options should appear, here is what MS UX style guide recommends:
List the options in a logical order, such as most likely to be
selected to least, simplest operation to most ...
I would strongly suggest you go with the first option but with a change.
The second option introduces a programatic step (selecting from the dropdown) that the user should not have to make - There is no requirement for this programatic step to operate as a 'safety catch' so it shouldn't be there.
The first option has a semantic problem - it's difficult to ...
What We Know So Far:
The first browser did not use Backspace to go back a page:
Several Mosaic menu or button functions have keyboard equivalents. Among them:
b, equivalent to the Back button
First Netscape Navigator (evolved from Mosaic) Did Not Use Backspace
I don't know how it started but I can add my two cents about what ALL my clients say:
$%!$% what the @$#%#% just happened? Why did the page change? Now I have to fill in that form all over again.
I would love to see this go away for good, and the first thing I do when building a form laden website is the following jQuery script:
var hasfocus = 'false';
By definition, a filter is a tool that help users narrow down to a subset of results that is most interesting to them. Consequently, when a filter is active, the results displayed should be less than the total number of original results.
For this reason, I find option B not intuitive enough. If I'm not mistaken, option B treats the icons using an additive ...
If the filter is mandatory, choose the most frequent search as the default.
You can try a scoped search dropdown before the search input field. This way the search button is Active from the beginning.
Lead with what your metrics show that the majority of users will want to search by, and don't make them pause to choose a filter.
If you have ...
Yes, the "I agree box" being defaulted to off is legal issue not a UX one. You'll want to get your solution approved by your legal team; different teams have different standards and there's no one "most legal" way to do it, so that I have to leave to you.
Arguably there's a UX issue here in trying to make sure users read your legalese, but I'll consider ...
How did this come about?
In 2005 this was implemented on Mozilla Firefox for the following reasons:
The backspace key was mapped to the browser ‘Back’ function in Mozilla for consistency with Internet Explorer. However, to improve consistency with other applications running on Linux, it was decided that this mapping should be optional—and set based on ...
I remember GitHub had something like what Mike M suggested for their search. I just noticed that it's changed, and what they do now is make the selection a part of their autocomplete-like menu:
I imagine the default selection at the top is what they believe to be the most common, which makes sense to search in the current repo by default. An advantage I ...
Mixing opt-in and opt-out is totally bad UX as it leads to a lot of confusion. The meaning of both lists should be consistent, so there should be either opt-out or opt-in for both groups:
Do you want to receive information from us by:
post phone email SMS 
Do you want to receive information from our carefully selected
It's your call whether it should be Yes/No or No/Yes. But it should be consistent across the entire app. This poses a concern for your reasoning because in some places Yes might be the default option and No might be default somewhere. Even though they are both within the same page / app.
A good workaround would be to use verbs. Save / Don't save is better ...
I don't think it is related to UX. The reasoning behind is that if you require the user to check that she have read the agreement, the fact that she doesn't is her fault. If the checkbox is checked by default, the user can simply say that she never checked anything, and just submitted the form with default values.
In other words, making it harder to fill ...
You shouldn't set a default for a birthday. Just as you shouldn't set a default for:
Credit card number
Credit card expiry date
The line of reasoning goes like this:
Usability is a measure of performance load, which is broken down to:
Cognitive load - the effort users expend when perceiving, interpreting and making decisions ...
Essentially, your users can either select one of your suggestions, or input their own custom name, so I'd present all of these in a single radio button list. This would present your automatic suggestions, but also communicate the option of customizing the embossing name, all while still limiting them to a single selection.
Opt-in vs opt-out is a legal question and (if it's for communication) in most countries (USA and Europe included). Any agreement to communicate with someone has to be an opt-in, otherwise that communication is legally spam, and anyone receiving it (in a country where it is illegal) may sue you. In fact there are people who make their living suing people ...
I think this depends a lot on how users interact with the field and how they change the default value. If, for example, the default value acts like placeholder text, then a 'clear' symbol such as an 'x' will do the job.
download bmml source – Wireframes created with Balsamiq Mockups
However, if the field can be left clear, with no value, then I would ...
Since this is a mandatory tasks before interacting with search, consider search like the Call to action like save or submit. Before you can accomplish these actions you must fill out a form.
In this case your form is a radial group and a text input field.
That feature is inherited from windows explorer feature, that migrated to Internet Explorer and then to other browsers. It became a de facto standard, due that most computers had Windows and Internet Explorer
I would say that putting an extra button there is generally a bad idea for the reasons you stated; you expect there to be just three buttons, and you accidentally click the "switch user" button a lot.
Now, here's why it is a bad idea:
The Icon for switch user is fairly similar to the minimize Icon
Switching users is probably used far less than minimize/...
The only application I know which puts an additional button there is Display Fusion (a software to improve the experience with multi-monitor setups).
That extra button moves the window to the other monitor:
In this case I would say this is appropriate since the associated action controls the window in a similar manner as the other buttons and I'm using it ...
Whenever you ...
I don't think there's a single right answer here—it depends on the likely behaviour the user will want based on what you're searching for. If there is a very high volume defaulting to a single day is a good thing.
For some kinds of data it's very likely the user will want the "to" date to default to now/today.
For some kinds of data they'd want the "from" ...
OkCupid has an interesting way of dealing with this that you may want to take a look at.
Basically, you can add filter criteria by selecting an additional one from the Advanced dropdown list, and you can remove existing filters (other than the basic ones) by selecting the x on the right of the optional filter.
This has the advantage that only the filters ...
Good question, it has bugged me in the past.
From W3C - Audio Control:Understanding SC 1.4.2, it seems that pages that do not offer sound control, or mute, functionality are not adhering to the criterion. Summarising the link:
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to ...
In the example below the secondary option has draws much less attention than the primary option. How you do that is up to you. Different situation but same issue.
The other thing that doesn't help in your design is that it's very crowded. Try to use more whitespace.
The most appropriate answer is "it depends", I reckon.
First of all, I'd say there isn't one most appropriate date for the events like graduation (which can be anywhere between this year and past centuries if we take the deceased into consideration) or birth date (idem).
I'd rather ask - can you afford setting a default year for each instance of the date ...