Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Validate and format it when the user exits the field. </p> </blockquote> <p>Yes. Provide noninvasive feedback to the user if validation or formatting rules fail. By noninasive I mean don't popup an alert or modal dialog box, thereby forcing the user to click something. Rather dynamically display a message adjacent or underneath the field where validation or formatting failed.</p> <blockquote> <p>Validate and format on every character entered. </p> </blockquote> <p>No. I think that hinders usability. Instead provide the user with a tooltip or some other hint as to what the formatting rules are or validation rules are. E.g. for a "required" field the practically ubiquitious asterisk, and for fields with formatting tell the user up front what the expected format is.</p> <blockquote> <p>Intercept keystrokes and prevent the user from entering characters that are wrong. </p> </blockquote> <p>If you are going to prevent the user from entering invalid characters, tell the user why you just blocked their input, noninvasively. Also,do not steal focus of the field. </p> <p>So for me the general principles are:</p> <ol> <li>Inform the user up front about your validation and formatting rules.</li> <li>Do not assume the user is sighted, so keep web accessiblity and screen readers in mind. (Unless you are developing a web site that has a limited target audience such as an Intranet.)</li> <li>Provide the user with noninvasive feedback, meaning do not make the user click on an alert box or modal dialog upon each failure.</li> <li>Make it obvious which input box failed validation or formatting rules, and tell the user why their input failed.</li> <li>Do not steal the mouse/pointer focus, when providing feedback.</li> <li>Keep tab order in mind, so that when keyboard oriented users complete a field, they can hit tab and go to the next logical input/selection field.</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload