720 reputation
1818
bio website wesleymurch.com
location Mystic, CT
age 33
visits member for 3 years, 8 months
seen Dec 23 at 7:29

Thanks for your interest.


Jan
19
awarded  Teacher
Jan
19
comment What makes a good newsletter good, from a UI point of view?
Opt out link in the message body? Maybe I've misunderstood you, but I would never look for it anywhere but at the bottom of the email. Making something like that harder to find by putting it in the message body does not seem like a good idea.
Jan
19
comment Would it be bad design (and unsafe) to put password guidelines next to a login box?
The funny part is that restricting password formats in the first place actually makes certain kinds of "jiggery-jaggery" easier.
Jan
19
comment Is the color red really appropriate for form validation errors?
Or are you just saying "Whether it's a good choice or not, red is already the standard, so just use it because that's what users expect"?
Jan
19
comment Is the color red really appropriate for form validation errors?
What would be an example of a "warning"? Form validation errors can be fixed by the user (the email was not typed correctly) , while system errors can not (the email was not sent because of some system failure), so I feel there should be some distinction in the way they are presented or the user may not immediately be able to tell the difference ("Do I stop or continue? Do I have to fix something?").
Jan
19
comment Is the color red really appropriate for form validation errors?
I'd say it's pretty significant, as every site I run has validation errors. It's been a question I've had for a long time, so I'm not exactly losing sleep over it. There must be something to it if virtually every website uses red for these kinds of errors, or maybe it's just an oversight or habit. I think if it can be answered in a non-subjective way, this would be the place, right? If not, I'll leave it up to the community to close the question.
Jan
19
comment Is the color red really appropriate for form validation errors?
Have I assumed too much about "red" being the standard, or am I just being naive? I pretty much never see any deviation from it. Even on this site, validation errors are red: i.stack.imgur.com/2K4yA.png (I also find the "oops" very annoying, but that's another topic).
Jan
19
asked Is the color red really appropriate for form validation errors?
Nov
7
awarded  Nice Question
Nov
5
comment Examples of placebos in UI design?
I think in this case, sometimes the intermediate page itself is the placebo and there's no real need to show it other than to let the user feel like something is happening.
Nov
4
comment Why is it impossible to deselect HTML “radio” inputs?
@Inca: That's maybe the most compelling answer I've heard so far.
Nov
4
comment Why is it impossible to deselect HTML “radio” inputs?
@Jon: Your suggestion to use checkboxes but restrict to one selection... doesn't that break expected behavior for checkboxes? I know it would trip me up. Why would you hack checkbox to save radio? If no one expects clicking a radio to deselect it, and won't generally try to re-click it, then what expectation is actually being broken? All I can see is benefit.
Nov
4
comment Why is it impossible to deselect HTML “radio” inputs?
@DA01: Yep, that's what I usually do, and why I use radios for forcing single choice. Using native checkboxes for that is not the right choice. It just strikes me as odd that a radio group can start off all unchecked, but going back to that state is impossible.
Nov
4
comment Why is it impossible to deselect HTML “radio” inputs?
@peteorpeter: The client ended up folding to my pressure to keep the "blank" radio selection. As far as the technical side: It's easy enough to do, but in light of the viewpoints here I've come to my senses, and won't be hacking anything.
Nov
4
accepted Why is it impossible to deselect HTML “radio” inputs?
Nov
4
comment Why is it impossible to deselect HTML “radio” inputs?
@Jon: You can unpush the pause button on 80's tape players, but the thing is we're talking about the web - an entirely different medium, so I don't see it as relevant.
Nov
3
comment Why is it impossible to deselect HTML “radio” inputs?
Checkboxes are not an option because they can't be used to force a single selection from many (at least natively). I understand this breaks some users' expected behavior, but I don't see why this particular idea is a bad one. Can you offer an example? How could this possibly trip someone up? Accidental double click? That's all I can think of.
Nov
3
comment Why is it impossible to deselect HTML “radio” inputs?
From a technical perspective, I'd rather use radios and fallback to radio behavior in case of a problem with the hack, to avoid multiple values being posted when only one is expected. So, what would you do if you were desperate to uncheck a radio? I would definitely try clicking it again, even if I know it won't work (while hoping it will).
Nov
3
revised Why is it impossible to deselect HTML “radio” inputs?
edited title
Nov
3
comment Why is it impossible to deselect HTML “radio” inputs?
I get what the control is trying to emulate, but I just don't see why this is needed on the web (the context in question). It seems like there should be a way to opt out of that behavior, or maybe another input type altogether. I feel like your first statement about not selecting default values (which I agree with) doesn't align with your statement that having no value selected "doesn't make sense".