I disagree with your second point, AJ. In an 'Error Correction Guidance' pattern I am working on at the moment, I recommend writing brief guiding message, which addresses most common errors *before* they occur.
So, in the example you have given, I would write: "The password should be at least six characters long. It should include numbers." -- Oleh Kovalchuke Interaction Design is design of time http://www.tangospring.com/IxDtopicWhatIsInteractionDesign.htm On Mon, Jul 7, 2008 at 8:12 AM, Alok Jain <[EMAIL PROTECTED]> wrote: > Suman, > > 1st part of the solution would ofcourse be how the forms are designed - to > prevent the error itself. > > If the error does happen, here aret eh things we have done with long forms: > 1. Display error as user moves from one field to the next and not on > Submission. This reduces the number of errors users have to deal with > 2. In our case we created a hierarchy of errors - for instance if a > password field was left blank - then we throw and error that it was blank > and not that it did not have minimum characters and it did not use a number > etc.. so only 1 error > > - AJ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
