Timeline for Mark or don't mark required fields if all are required?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 11, 2020 at 8:56 | comment | added | Oz Radiano | Out of context but can't ignore the 'clear input' ): | |
Nov 7, 2018 at 15:44 | comment | added | GlennG | Don't use colour to convey meaning alone.... When Chrome et-al pre-colour the fields yellow overriding your explicit instruction. w3.org/TR/WAI-WEBCONTENT/#gl-color | |
Feb 4, 2014 at 9:14 | comment | added | uxfelix | My intention is to guide (and not force) the users focus to those fields that are required. My example might look a bit harsh: Exchange the "x"'s with a left pointing arrow, take away the red and surround the unfilled input fields with green (while keeping the filled in fields filled green). Then they won't look like errors but will prevent the user from making mistakes in the first place. @Bill | |
Feb 3, 2014 at 21:51 | comment | added | Bill Dagg | @uxfelix: Disagree. Suggesting to the user that they made an error before giving them the chance to fill in the required information is not good UX. From the user's perspective "Stop telling me I've done something wrong. Give me a chance. I haven't even got there yet!" | |
Jan 20, 2014 at 15:52 | comment | added | uxfelix | If those fields that are mandatory and have not been edited yet are marked red before the user hits send, chances are much higher he/she will fill them in before hitting send and running into an error. @Ruslan | |
Jan 20, 2014 at 15:19 | comment | added | Ruslan | I'd say premature color-marking distracts the user from the actual form content. Better colorize only if "Send" has been clicked with incomplete form. | |
Jan 20, 2014 at 10:59 | history | answered | uxfelix | CC BY-SA 3.0 |