General discussion of network form availability specification

Reprinted from: An extensive Guide to Web Form usability

Author: Justin Mifsud

Small level Limited, lied, forget to forgive ~! It must be a ~!.

General discussion of network form availability specification

The following is a complete departure from what you will read, which is that it is not helpful to have a nice button, color, or even a full set of jquery plug-ins for your form. In fact, you've only achieved one-third of the availability of the form (through no warping way).

In this article, we will provide a practical and workable specification for you to implement. These carefully choreographed specifications are derived from usability testing, on-site testing, Web site tracking, line tracking, web analytics, and customer complaints received by support departments.

Why network form availability is so important

The ISO 9241 standard defines web site availability as "efficient and effective for specific users to achieve specific goals in an environment." "When using a site, the user has a specific goal." If the design is good, the site will achieve this goal and the site behind the organization's goals. Forms are often present in the midst of user goals and (site) organization goals, because, despite the evolving human-computer interaction, forms are still the dominant style of user action in the site. In fact, forms are often considered to be the last and most important part of accomplishing the goal process.

Let's explain this point by discussing the three major ways in which forms are used. Like Luke Wroblewski in his book (Web Form design:filling in the blanks Web Form design: filling gaps), each form is one of three main reasons: business, social, or productivity. The following tables translate these elements into the user/business objectives behind the reason:

The above table is referenced from the Luke Wroblewski ' s Web form design:filling in the blanks

In summary, there are two aspects to the relationship between the form and usability:

1. The form is a key point to whether the user can reach the target of use.

2. The form should help users to accomplish their goals easily.

This article focuses on the 2nd, because an easy-to-use form will naturally improve the whole site usability, and then the 1th.

6 components that make up a network form:

Web Forms are the key points and tangled points of designers and users. For a long time, users have formed an expectation of the visual and operational behavior of the form. They usually want the network form to have the following 6 components:

1. Label

Tell the user the meaning of the appropriate input area.

2. Input area

Input areas allow users to provide feedback. This includes the text input area, password input area, multiple options, single option, scroll bar, and so on.

3. Behaviour

Refers to a link or button, when the user clicks, performs an action, such as submitting a form.

4. Help

Help with filling out forms.

5. Information

Give feedback for user input. The user will be confirmed (such as a prompt for the successful submission of the form) or negative (' The username you entered is already in use ').

6. Confirms

These measures ensure that the data submitted by the user is recognized as an acceptable parameter.

Skype's registration form contains all 6 parts.

Achieve form availability in three ways

Despite differences in layout, functionality, and intent, all forms contain 3 large portions, as Caroline Jarrett and Gerry Gaffney in their books (Forms that work:designing Web forms for Usability Form implementation: Designing a form for availability:

1. Relationship

The form establishes the relationship between the user and the (Network platform) organization

2. Dialogue

Forms create a dialogue between users and organizations

3. Appearance

Build relationships and dialogs based on the appearance of the form

For an easy-to-use form, you should include these 3 parts. Let's look at it in turn, with practical specifications that are easy to implement, and then understand how to make the form really easy to use.

Part I: Relationship

"No one is isolated," the 17th century British poet, satirist, lawyer and pastor John Donne once said. Indeed, human beings are rich, loving, friendly, professional or commercial because of various relationships. The meaning of a form is to establish or enhance the relationship between the user and the organization. When this part is bad, the relationship ends.

There are some principles that need to be kept in mind:

1. Relationship based on trust

So building trust in your form is critical. This can be achieved by logos, images, colors, typography, and text. Users will actually feel the form coming from a (trustworthy) Frank organization.

2. Each relationship has a purpose

To be entertained in a romantic relationship or to achieve financial gain in a business relationship. Ask yourself, what is the purpose of your form?

3. Show intent based on form name

The name prompts the user for what the form is about and why the user must fill it out.

4. Mutual understanding

As in a relationship, it is important to know each other. Fully understand the user and often consider whether your problem is appropriate and timely. This will instill a natural flow into your form.

5. Select the appropriate language and remove the extra text

Knowing that the user will help you select the appropriate language and remove the extra text. It will help you create an interface that balances your needs and the needs of your users.

6. Do not ask questions that are beyond the scope of the form.

In a relationship, you may have doubts about those who ask for cross-border problems. This also happens in online mode. Take full account of the relevant participants and decide what information is really needed.

7. Sudden changes in behavior and surface

This can make users feel uneasy. In the same way, never insert a sudden change in a table or 2 steps in a form.

Know your users. Allow registered users to easily login, so that new users to facilitate registration. Debenhams the difference between those 2.

Amazon, on the other hand, simplifies the process for registered users and new users.

Part II: Dialogue

A form is a dialogue. Like a real conversation, the form takes on both sides of the two-way communication, where it refers to the user and the organization behind the online platform. In fact, the users who fill out the form are trying to communicate with the organization.

For example, for social networks, users can send information by filling out a form that they want to join. When processing a request (whether automated or manual), the (site) organization asks the user some questions, such as their name, email address, and so on. When accepted (or rejected), the (site) organization notifies the user of the results, thus completing the entire conversation process.

Here are some useful specifications:

1. The form of dialogue is not an interrogation

As mentioned before, the form is a dialogue, not an interrogation. Aggressive label words can irritate users, and (if they don't leave) they may give you the answers you want, not the facts.

2. Labels must conform to logic

The label must be logical to correspond to the natural flow of the conversation. For example, would it be strange to ask a user a lot of other questions and ask his name? Some related complex issues should be placed on the back of the form.

3. Group related information

such as personal details. The process of transferring from part of the problem to another part of the problem should follow a (real) dialogue.

Yahoo's Registry is a group of related content with purple headings and fine lines.

Constant Contact Group related content, but it put different components too open, causing users to confuse.

4. Talk about one topic at a time

In a real conversation, each label should only address one problem at a time, helping the user respond to the appropriate input area.

5. Natural Pause

The natural pause in the conversation is where to arrange white, how to group labels, and whether to scatter the form into multiple pages.

6. Remove complex (Element)

In any (real) conversation, people will be mad at the background noise. So remove clutter that might prevent users from filling out a form, such as banners or unwanted navigation.

Dropbox provides a good example of what makes the registration form look good. The white area looks good and the pages are neat.

Part III: Appearance

1. Label

A. Words vs. sentences

If the intent of a label is easy to understand, such as asking for a name or phone number, then one or two words is enough. But in order to eliminate ambiguity, sometimes phrases and sentences may be needed.

Amazon's registration form uses a complete sentence, although the word may be enough to explain the problem.

B. Sentence style vs. heading style

Should "name and Surname" or "Name and Surname" be used?

Compared to the heading style, sentence styles are easier to follow than the syntax. One thing is for sure, not all caps, which makes the form unprofessional and difficult to navigate.

How difficult is it to quickly browse the tags of the Barnes & Noble Registry (all of which are capitalized)?

C. The colon at the end of the label

Some desktop applications and operating platforms, such as Windows Interactive specifications, are highly recommended for appending a colon to the end of the form label. Some online form designers still adhere to this practice, mainly because of the old screen readers, most of them rely on a colon to identify a label. Some recent users rely on identities, especially for labels. In addition, the preference for colons is controversial and if the form style remains uniform, it does not increase or detract form availability.

D. label alignment: Top Align vs. left Align vs. right

As opposed to conventional advice, the area above the input box is not always the best place to put labels. It is an ideal combination for users to quickly fill out forms. But sometimes you want to slow down the user's reading so that users can more fully notice the label details. Of course, let a long form to keep a column, users easy to scroll the page, which is more than breaking information, composed of multiple columns to ensure that everything "patchwork" is much better. Each alignment has its advantages and disadvantages.

Time data reference from "Matteo Penzo label slide-up in Forms" (placing a label in a form)

(The form should not contain more than one column.) Taking the makeup geek page as an example, it's easy to ignore the vertical column information (not to mention the "required" annotation at the tail).

2. Input area

A. Type of input area

Provide the appropriate input area style as needed. Corresponding to user habits, each of the different types of input boxes have their own characteristics. For example, using radio buttons for single selection results, multiple options use check box.

B. Customizing the input area

Do not create new input area styles. This was very much seen on the early flash site and is now resurgent; I've seen the bizarre input area design developed with jquery. Simplicity is often the easiest to use. Move the input area styles closer to the original HTML style as much as possible.

Highlighting the input area can make users wonder.

C. Restricting input area formatting

If you have to limit the format of user input data, at least do not use the method that annoys the user. For example, instead of displaying yyyy in the input box to prompt the user, consider providing 3 drop-down or selecting a calendar.

D. Required fields vs. optional

A clear distinction between the user can not be left white input box. The general method is to use the asterisk annotation (*). As long as you can explain your intentions, use any element, even an asterisk.

3. Behaviour

A. Main actions vs. secondary behavior

The main behavior is that links and buttons are necessary to complete the "final" function, such as "Save" and "submit." Secondary behavior refers to "return" and "Cancel" so that users can undo the data they have entered. If you click on the error, the secondary behavior will basically result in unintended results, so try to use the main behavior if possible. If you have to use a secondary behavior, the visual weight of the main behavior weakens the secondary behavior.

The lack of a significant difference in primary and secondary behavior can lead to failure. Look at the St. Louis Community Eton site on the lengthy registration form button on the register, imagine if the wrong operation point "reset form" ...

B. Naming conventions

Avoid naming behavior in generic terms such as "commit," because it makes the form look mediocre. Use descriptive text and phrases, such as "joining LinkedIn" for better.

Although Coca-Cola correctly promoted the importance of the main action button, it used a generic "submit" as a button description, and it would be more helpful to use "Join us".

4. Help

A. Form accompanying hints

You should never have the opportunity to explain to the user how to fill out the form. If it doesn't look like a form or is particularly complicated, then redesigning may be your only option. Accompanying prompts should be used where necessary, such as explaining why credit card information is required or how birthday information is used or associated with the "usage term." This kind of information is easy to ignore, so make it concise and easy to read. So the rule is: Don't let the explanation (EC) exceed 100 words.

B. User triggers and automatic help

It's better to show it when you need it than to give it a hint on every input frame. You can place a small icon near the input box and click it when the user needs help with this area. A more perfect solution is to automatically display prompts when the user activates the input box to enter data. This kind of effect is more common and easier than using JavaScript libraries such as jquery.

Skype's registration form contains user-triggered Help (a blue box triggered by clicking the problem ID above) and automatic Help (recommended username)

5. Information

A. Error tips

This type of information prompts the user for an error and is often used to prevent the user (in case of an error) from being too deep into the form process. The error message can be highlighted in the following ways: color (usually red), familiar image symbols (such as a warning mark), highlighting (usually around the top of the form or at the location where the error occurred), large fonts, or using these methods in combination.

B. Success tips

Use a success hint to tell the user that he has reached a meaningful node in the form process. If the form is too verbose, a success message encourages the user to continue to fill it out. As with the error hint, the success hint should also be highlighted. However, it does not hinder the user's form process.

6. Confirms

A. appear only where needed

Too much acknowledgement is as bad as no acknowledgement, as it can make the user tired. Validation should be limited to key points (such as user name availability), ensuring meaningful answers (such as not allowing age over 130) and giving constructive answers, such as the face of a limited but long list of answers (such as the prefix of the country code) to be displayed with a dropdown.

B. Smart defaults

To ensure that the user completes the form faster and more accurately, set the smart default value. For example, based on user IP address preselection user country. Use this feature sparingly, however, as users tend to place pre-filled portions (without confirmation).

Twitter's registration form uses automatic confirmation (for name, email address, password and username) and smart defaults ("Stay logged in").

(conclusion) Start

The word "conclusion" is not exact here. Let this be the starting point for applying what I write to your own form. The good news is that there's so much more to say, you can find enough resources for each point. Here are three books for you to start with: As I wrote at the beginning, adjusting the user (visual) interface as a shortcut does not make your form available. What more can I say? The point is that you. Come on, move your hands.

Extended Reading

* Forms that work:designing Web forms for usability, Caroline Jarrett and Gerry Gaffney

* eyetracking Web Usability, Jakob Nielsen and Kara Pernice

* Web Form Design, Filling in the blanks, Luke Wroblewski

The author of this article: sealed can reprint please specify from: Ctrip ued