3. Sure. We make a lot of assumptions when building
websites. But the important thing about those assumptions is when things go
wrong how will it affect the user? Someone has a black & white screen? Well
they wouldn't see the colors anyway. Not a BIG deal. They know they're monitor
doesn't work with color already. Website is wider than the screen size? Kind of
annoying because the user now has to scroll to see your content. A bit of an
inconvenience and probably unexpected but it's livable. User can't navigate to
another page because they have an old version of a screen reader and your
navigation uses a dropdown with an onchange event? Not good at all. You've shut
that user out almost completely. You've also shut out search
engines.
My original point of that question (as I stated in another
email) is that of data security. Relying on js for data validation is a big
mistake. The same validation steps need to be taken on the server side. If
you're relying on js in a form for validation already you might as well take the
validation from the client-side to the server-side and submit the form through
AJAX (showing the results on the return call).
4. Agreed.
5. I find this strange. Do you have any public studies
you can cite?
Thanks,
Chris.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glen Lipka
Sent: Tuesday, November 14, 2006 11:47 AM
To: jQuery Discussion.
Subject: Re: [jQuery] How to display error/validation messages?
I organized the answers inline. This probably breaks email
ettiquette. - Glen
1. Bigger text fields. Many (most?) users have sketchy vision and
flickering monitors. Make the text boxes bigger and they will be
happier. Same goes for the submit buttons.
2. Have a visual indication next to required fields (background color,
asterisk, something). Make sure they see it.
3. Do not submit the form if the required fields are not filled in.
(Click sign in on mine to see sample interaction.) Light up the error
fields. Turn them back to normal when the user focuses on them.
3. This is assuming that
_javascript_ is enabled right?
Yes. Although, at this date, I
actually believe in forcing the user to have _javascript_ on. I am making
alot of assumptions. Color monitor, screen resolution, modern browser that
understands CSS. I do believe in delighting 96% of the audience even at
the expense of the 4%, but you have to know your audience and
circumstances. I don't think you should ignore accessibility just because
the disabled are small, for example. Hmm, I guess there is some to think
about here.
4. Allow for keyboard TAB input as well as mouse click input.
Remember, sometimes users cut/paste.
4. When would tabbing not be allowed? Also, the tabbing in
your sample form is all out of whack. I think it's best to not adjust the
tabbing order.
Yes, it's out of
whack. But it SHOULD work. Use tabIndex specifically when
the default order doesn't make sense to the user. My example was made
a little too quickly. :) I think keyboard interfacing is pretty common and
should be encouraged. Gmail allows for control-s to save, for example.
5. Give inline errors in red when they screw up (Put an invalid email in
the email field and then click on the next field. This falls into the
design principle called "Constraints". Lego is a great example of how to
do this right. Never allow the user to do something incorrect.
Always disallow bad entry. (Garbage In-Garbage Out)
5a. When I
put in my email address incorrectly (on purpose) and tabbed to the next field I
received an error (I like your implementation). But I also saw that the data I'd
entered was removed. How annoying! What if I simply forgot to put a period in my
long email address? Now I have to type the entire thing over again and possibly
make the same mistake.
That was a concern, but
we looked at usability tests and concluded that the more "power-user" the person
was, the more they found it annoying, and the more "newbie" the person was, the
more they found it helpful. But power users don't get frustrated and quit,
while newbies do, so we erred on the side of helping the newbie.
5b. What is "Lego is a great example..."? Do you mean Lego as in the
building bricks? How does that relate to web usability?
Its about
constraints. Don Norman relates this in his book, The Design of Everyday
Things (DOET). He talks about how Lego makes all of their products in a
way that it is near impossible to use incorrectly. Make your web forms
impossible to use incorrectly. Help the user by creating interaction that
limits his behavior.
6. Eliminate instructions. Users NEVER read instructions, so you
might as well get rid of it and focus on getting them through the process
without it. Users will read phrases and words, but not sentences. As Don
Norman (Godfather of Design) says, "A door that -requires- a sign that says
[Pull] is a porrly designed door".
6. I couldn't agree
more!!
Woo Hoo!
My profession is a UX Designer. jQuery is a great tool for
the UX Designer because it allows more design principles to be implemented
quickly in a prototype. This, then, is easier to hand off to more
programmatic folks in the engineering dept. Often I find, that the
engineers don't want to include the interactivity because they don't see the
value and don't want to "write all that _javascript_ code". jQuery
eliminates that problem and actually makes them EXCITED about _javascript_.
_______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
