New answers tagged labels
If Order Status and Order History are about take-out orders, my suggestion for the section naming would be Eating Out & Takeaways. If the Orders are about going out to restaurants yourself, then just Eating Out.
Choosing the correct labels is best left to someone who is familiar with the app; with the client base and who is a native speaker. Ideally he would be a professional writer as well but I'll give it a go. How often do you use this application? [ ] I use it multiple times per day for work. [ ] I use it several times a week for work. [ ] I use ...
Chattier is never likely a UX improvement. However, having a casual voice or plain language explanation could be. In other words, don't make labels wordier for the sake of being wordier. Do make them fit the overall personality and objectives of your site/form. When it doubt, though, keep it simple (and short).
My suggestion would be to make no compromises, as a user will more often find it hard to remember a certain variable name, so I'd look at what is known already. First of all, as the user types stuff, some autocomplete helper could kick in and provide suggestions. Than, if the word actually is a variable name, I'd simply visually show this e.g. When ...
First Approach I think that you should make the text of required fields red, either #F00 or similar brightness, and clearly indicate what that means beforehand. This approach is more noticeable, and harder to miss than the classic "red asterisk" approach, but is still reminiscent of it. Another thing to keep in mind is when to let your users know a field ...
To answer your specific question " is there an established pattern for this kind of thing?", the the answer is YES, THERE IS. http://www.formsthatwork.com/Appearance Best practice for indicating required fields Guess what: users don't care about required field indicators very much either. OK, we admit that a few of us webby-geeky types know what ...
Marking a group title with an asterisk can be pretty confusing. How about writing in plain English? Something like "You must provide your phone or email address". Also, if you don't want users to provide both, you can combine those fields into a single field and call it "Phone or Email". And you'll be able to put asterisk on that label.
Sounds like you're building a system that only lets them enter one method of contact. That's not optimal. One contact type should be the minimum, not the maximum. What DasBeasto says (plus some comments on his answer) is a long way in the right direction, but not quite there. Using the asterisk on a section instead of a field should be clear enough, but I ...
Never rely on colour alone to convey meaning as this will cause problems for users with varying types of colour blindness.
The confusion isn't coming from the color of the double asterisk, it's the double asterisk itself that isn't intuitive. I've always believed if you need a legend to detail what your page is saying to users then you're saying it wrong. Instead I would give each field set a header such as Contact Info, Parents Contact Info, etc. then say "Choose one" and put ...
You don't need the double asterisk if you can group related fields together and label them (example: "Contact Information") and then place the asterisk by the label "Contact Information." (you can add "Select one of the following" below) Here's a rule-of-thumb: if you have to explain too much it's too complicated.
From my point of view, there is few things to consider Chatty kind of labels are rather new so users might not expect them Chatty labels will take more time and the form will take more time to fill Also these chatty labels if they are very long, they might shift to two lines on a small mobile screen so again more readability problems Here is how i used ...
It depends on the overall experience you want to provide the user. For example: If you want to provide a more professional experience to the user and want to make it look legitimate and serious, you could go ahead with using only the relevant tag as the label, let's say: Name: If your plan is to not be as serious but provide a fun, intuitive experience, ...
That depends on whether the selection within each facet is mutually exclusive. So Author if you can only select one author; authors is you can select more then one. Respectively, this can be seen as whether category items use checkboxes vs radio buttons / links. Compare: To:
Singular, because the final selection is would read as Author : Christopher Alexander
While the order matters in deciding the label position (whether label should appear before or after the input), it doesn't matter in code as long as the IDs in id and for are the same -- the input and label will still be linked -- see the example on this fiddle. Alternatively, you could wrap the <input> inside the <label>: <!-- nested, text ...
Top 50 recent answers are included