Any optional fields should be explicitly denoted as such too, so that users can read the field label and understand its context and conditions without having to infer them from surrounding fields.
9xchatsex - Paypal validating address information
This is particularly true of form fields where users often focus only on the field they are currently filling out, largely ignoring the other fields in the form.
It’s therefore important to good form usability that each field can be understood in isolation, and for this exact reason it’s insufficient to simply mark all required fields with an asterisk.
It may seem like a small detail, but it’s actually especially important to get right for the address fields because they are related, and some users may therefore assume that if ‘line 1’ is required then ‘line 2’ is as well.
(See all our test findings on explicitly marking both required and optional fields) If you’ve found there’s a low utilization rate for the ‘Address Line 2’ field, you can consider removing or hiding it entirely. If you don’t need to distinguish what data belongs to each address line, the most simple solution is to consider just having a single ‘address’ field.
gift and flower sites which often have both a ‘giver’ and a ‘receiver’, or orders with different billing and shipping addresses).
So while this sub-issue of misinterpreting the address fields as two different addresses is low in frequency, the severity of it when it does occur is very high.In this article we’ll therefore go over 5 tips to get the ‘Address line 2’ right.The first step is to query your order history and figure out how much the ‘Address Line 2’ field is currently being used, who is using it, and the type of information they are filling into the field.All of this can prove valuable insights when it comes to optimizing the field context (tip #2) with precise labelling and useful instructions and placeholder text.It may also help you better predict any edge use-cases (and by virtue thereof, better support those).The most commonly observed issue with the ‘Address Line 2’ field during our usability test sessions are field ambiguity, with users often wondering Even something as common as an apartment address, where it’s clear that street name and number should go in the first address field, we time and again see test subjects turn doubtful as they have to type a floor level or room number.