Showing posts with label Usability Guidelines. Show all posts
Showing posts with label Usability Guidelines. Show all posts

Writing Web Content

0 comments

Writing Web Content is the most important part of a Web site. If the content does not provide the information needed by users, the Web site will provide little value no matter how easy it is to usethe site.

When preparing prose content for a Web site, use familiar words and avoid the use of jargon. If acronyms and abbreviations must be used, ensure that they are clearly understood by typical users and defined on the page.

Minimize the number of words in a sentence and sentences in a paragraph. Make the first sentence (the topic sentence) of each paragraph descriptive of the remainder of the paragraph. Clearly state the temporal sequence of instructions. Also, use upper- and lowercase letters appropriately, write in an affirmative, active voice, and limit prose text on navigation pages.


Make Action Sequences Clear:
  • When describing an action or task that has a natural order or sequence (assembly instructions, troubleshooting, etc.), structure the content so that the sequence is obvious and consistent.
  • Time-based sequences are easily understood by users. Do not force users to perform or learn tasks in a sequence that is unusual or awkward.

Avoid Jargon:

  • not use words that typical users may not understand.
  • Terminology plays a large role in the user's ability to find and understand information. Many terms are familiar to designers and content writers, but not to users. In one study, some users did not understand the term 'cancer screening.' Changing the text to 'testing for cancer' substantially improved users' understanding.
  • To improve understanding among users who are accustomed to using the jargon term, it may be helpful to put that term in parentheses. A dictionary or glossary may be helpful to users who are new to a topic, but should not be considered a license to frequently use terms typical users do not understand.

Use Familiar Words:
  • Use words that are frequently seen and heard.
  • Use words that are familiar to, and used frequently by, typical users. Words that are more frequently seen and heard are better and more quickly recognized. There are several sources of commonly used words (see Kucera and Francis, 1967 and Leech et al., 2001 in the Sources section).
  • Familiar words can be collected using open-ended surveys, by viewing search terms entered by users on your site or related sites, and through other forms of market research.

Define Acronyms and Abbreviations:

  • Do not use unfamiliar or undefined acronyms or abbreviations on Web sites.
  • Acronyms and abbreviations should be used sparingly and must be defined in order to be understood by all users. It is important to remember that users who are new to a topic are likely to be unfamiliar with the topic's related acronyms and abbreviations. Use the following format when defining acronyms or abbreviations: Physician Data Query (PDQ). Acronyms and abbreviations are typically defined on first mention, but remember that users may easily miss the definition if they scroll past it or enter the page below where the acronym or abbreviation is defined.

Use Abbreviations Sparingly:
  • Show complete words rather than abbreviations whenever possible.
  • The only times to use abbreviations are when they are significantly shorter, save needed space, and will be readily understood by typical users. If users must read abbreviations, choose only common abbreviations.

Use Mixed Case with Prose:
  • Display continuous (prose) text using mixed upper- and lowercase letters.
  • Reading text is easier when capitalization is used conventionally to start sentences and to indicate proper nouns and acronyms. If an item is intended to attract the user's attention, display the item in all uppercase, bold, or italics. Do not use these methods for showing emphasis for more than one or two words or a short phrase because they slow reading performance when used for extended prose.

Limit the Number of Words and Sentences:

  • To optimize reading comprehension, minimize the number of words in sentences, and the number of sentences in paragraphs.
  • To enhance the readability of prose text, a sentence should not contain more than twenty words. A paragraph should not contain more than six sentences.

Limit Prose Text on Navigation Pages:

  • Do not put a lot of prose text on navigation pages.
  • When there are many words on navigation pages, users tend to rapidly scan for specific words or begin clicking on many different links, rather than reading the text associated with the links.

Use Active Voice:

  • Compose sentences in active rather than passive voice.
  • Users benefit from simple, direct language. Sentences in active voice are typically more concise than sentences in passive voice. Strong verbs help the user know who is acting and what is being acted upon. In one study, people who had to interpret federal regulation language spontaneously translated passive sentences into active sentences in order to form an understanding of the passages.

Write Instructions in the Affirmative:

  • As a general rule, write instructions in affirmative statements rather than negative statements.
  • When giving instructions, strive to tell users what to do (see a dentist if you have a toothache), rather than what to avoid doing (avoid skipping your dentist appointment if you have a toothache). If the likelihood of making a wrong step is high or the consequences are dire, negative voice may be clearer to the user.

Make First Sentences Descriptive:

  • Include the primary theme of a paragraph, and the scope of what it covers, in the first sentence of each paragraph.
  • Users tend to skim the first one or two sentences of each paragraph when scanning text.

Source:[usability.gov]

Screen-Based Controls (Widgets)

0 comments

In order to interact with a Web site, users usually require the use of screen-based controls (sometimes known as 'widgets'). Besides the pervasive link, commonly used screen-based controls include pushbuttons, radio buttons, check boxes, drop-down lists and entry fields. Designers should ensure that they use familiar widgets in a conventional or commonly-used manner.

When pushbuttons are used, ensure that they look like pushbuttons and that they are clearly labeled. In some cases, the pushbuttons will need to be prioritized to facilitate their proper use.

Radio buttons are used to select from among two or more mutually-exclusive selections. Check boxes should be used to make binary choices, e.g., 'yes' or 'no.' Drop-down lists are generally used to select one item from among many. To speed user performance, show default values when appropriate, and do not limit the number of viewable list box options.

Entry fields are used when completing forms and entering text into search boxes. Designers should try to minimize the amount of information entered by users. Each entry field should be clearly and consistently labeled, with the labels placed close to the entry fields. Designers should also clearly distinguish between 'required' and 'optional' data entry fields, and attempt to minimize the use of the Shift key.

To facilitate fast entry of information, designers should automatically place the cursor in the first data entry field, provide labels for each field (e.g., pounds, miles, etc.), and provide auto-tabbing functionality. In order to increase accuracy of data entry, partition long data items into smaller units, enable the software to automatically detect errors, and do not require case-sensitive data entries. Showing users their data entries can increase accuracy. For experienced users, the fastest possible entry of information will come from allowing users to use entry fields instead of selecting from list boxes.


Distinguish Required and Optional Data Entry Fields:
  • Distinguish clearly and consistently between required and optional data entry fields.
  • Users should be able to easily determine which data entry fields are required and which are optional. Many Web sites are currently using an asterisk in front of the label for required fields. Other sites are adding the word 'required' near the label. One study found that bolded text is preferred when compared to the use of chevrons (>>>), checkmarks, or color to indicate required fields.

Label Pushbuttons Clearly:
  • Ensure that a pushbutton’s label clearly indicates its action.
  • The label of a pushbutton should clearly indicate the action that will be applied when the pushbutton is clicked. Common pushbutton labels include 'Update,' 'Go,' 'Submit,' 'Cancel,' 'Enter,' 'Home,' 'Next,' and 'Previous.'

Label Data Entry Fields Consistently:
  • Ensure that data entry labels are worded consistently, so that the same data item is given the same label if it appears on different pages.
  • If possible, employ consistent labeling conventions. For example, do not use single words or phrases for some labels and short sentences for others, or use verbs for some and nouns for others.

Do Not Make User-Entered Codes Case Sensitive:
  • Treat upper- and lowercase letters as equivalent when users are entering codes.
  • Do not make user-entered codes case sensitive unless there is a valid reason for doing so (such as increased security of passwords). If required, clearly inform users if they must enter codes in a case specific manner. When retaining data entered by users, show the data as it was entered by the user.

Label Data Entry Fields Clearly:

  • Display an associated label for each data entry field to help users understand what entries are desired.
  • Employ descriptive labels that clearly, concisely, and unambiguously define the required entry. Make labels distinct enough so that readers do not confuse them with the data entries themselves. This can be done by bolding the labels or providing other visual cues, such as an asterisk.
  • Do not create new jargon when labeling data entry fields. Use common terms (e.g., male, female) rather than arbitrary labels (e.g., Group 1, Group 2). If the meaning of a proposed label is in doubt, conduct usability testing with an appropriate sample of qualified users.

Minimize User Data Entry:
  • Do not require users to enter the same information more than once.
  • Requiring re-entry of data imposes an additional task on users, and increases the possibility of entry errors. When entries made by users on one page are required on another page, the computer should retrieve the original entries, rather than requiring re-entry of the same information. In general, require users to make as few entries as possible.

Put Labels Close to Data Entry Fields:
  • Ensure that labels are close enough to their associated data entry fields so that users will recognize the label as describing the data entry field.
  • All labels and related information should be close to the data entry field to enable users to easily relate the label and entries required.

Allow Users to See Their Entered Data:
  • Create data entry fields that are large enough to show all of the entered data without scrolling.
  • Users should be able to see their entire entry at one time. There always will be some users who will enter more data than can be seen without scrolling; however, try to minimize the need to scroll or move the cursor to see all the data for that field. If there is a character limit for a particular field, state that near the entry field.
  • Designers should be particularly aware of the length of data entry fields used for entering search terms. One study found that this entry field should be at least 35-40 characters long to accommodate ninety-five percent of search terms being used.

Use Radio Buttons for Mutually Exclusive Selections:
  • Provide radio buttons when users need to choose one response from a list of mutually exclusive options.
  • Radio buttons should be used when there is a need to select from among mutually exclusive items. Users should be able to click on the button or its text label to make their selection. Assign one of the radio button choices as the default when appropriate. One study reported that for making mutually exclusive selections, radio buttons elicit reliably better performance than drop-down lists. Radio buttons are also preferred over both open lists and drop-down lists.

Use Familiar Widgets:
  • Use widgets that are familiar to your users, and employ them in their commonly used manner.
  • Do not assume that all users are familiar with all available widgets. Unfamiliar widgets will slow some users, and cause others not to use the widget because they do not know how to make it work properly. For instance, one study showed that some users, particularly older users, do not know how to use a drop-down list.
  • In choosing widgets, designers typically consider such issues as the amount of available screen 'real estate,' reducing the number of user clicks, and whether the user will be choosing one from among many items, or several items at once. Usability test the performance and acceptability of widgets to ensure they do not confuse or slow users.


Anticipate Typical User Errors:

  • Use the computer to detect errors made by users.
  • Do not expect that users always will make correct entries. Anticipate possible user errors, and when possible, allocate responsibility to the computer to identify these mistakes and suggest corrections. For example, if a date is entered as 'February 31,' the computer should generate an error message asking for a revised entry.
  • Design the site's search engine (and other places where users enter data) to accommodate common misspellings and certain other errors.

Partition Long Data Items:
  • Partition long data items into shorter sections for both data entry and data display.
  • Partitioning long data items can aid users in detecting entry errors, and can reduce erroneous entries. For example, it is easier to enter and verify a ten digit telephone number when entered as three groups, NNN-NNN-NNNN. Similarly, ZIP+4 codes and Social Security numbers are best partitioned.

Use a Single Data Entry Method:
  • Design data entry transactions so that users can stay with one entry method as long as possible.
  • Do not have users shift back and forth between data entry methods. Requiring users to make numerous shifts from keyboard to mouse to keyboard can substantially slow their entry speed.

Prioritize Pushbuttons:
  • Use location and highlighting to prioritize pushbuttons.
  • If one pushbutton in a group of pushbuttons is used more frequently than the others, put that button in the first position. Also make the most frequently used button the default action, i.e., that which is activated when users press the Enter key.
  • One study reported that designers should place the button most likely to be clicked on the left side of a two-button set of buttons. This button arrangement allows the user to read the first button label, and since it is the most likely selection, click on that button immediately. Some users look at the left and then right button before making a selection, preferring to be fully informed before submitting a response.

Use Check Boxes to Enable Multiple Selections:
  • Use a check box control to allow users to select one or more items from a list of possible choices.
  • Each check box should be able to be selected independently of all other check boxes. One study showed that for making multiple selections from a list of non-mutually exclusive items, check boxes elicit the fastest performance and are preferred over all other widgets. Users should be able to click on either the box or the text label.

Label Units of Measurement:
  • When using data entry fields, specify the desired measurement units with the field labels rather than requiring users to enter them.
  • Designers should include units such as minutes, ounces, or centimeters, etc. as part of the data entry field label. This will reduce the number of keystrokes required of users (speeding the data entry process), and reduce the chance of errors.

Do Not Limit Viewable List Box Options:
  • When using open lists, show as many options as possible.
  • Scrolling to find an item in a list box can take extra time. In one study, an open list that showed only three (of five) options was used. To see the hidden two items, users had to scroll. The need to scroll was not obvious to users who were not familiar with list boxes, and slowed down those that did know to scroll.

Display Default Values:
  • Display default values whenever a likely default choice can be defined.
  • When likely default values can be defined, offer those values to speed data entry. The initial or default item could be the most frequently selected item or the last item selected by that user. In general, do not use the default position to display a heading or label for that widget.

Place Cursor in First Data Entry Field:
  • Place (automatically) a blinking cursor at the beginning of the first data entry field when a data entry form is displayed on a page.
  • Users should not be required to move the mouse pointer to the first data entry field and click on the mouse button to activate the field. Designers should consider, however, that programming this automatic cursor placement might negatively impact the performance of screen reader software.

Ensure that Double-Clicking Will Not Cause Problems:
  • Ensure that double-clicking on a link will not cause undesirable or confusing results.
  • Many users double-click on a link when only one click is needed. Developers cannot stop users from double-clicking, but they should try to reduce the negative consequences of this behavior. Usability testing has indicated that if users start with quick double-clicks, they tend to continue to do this for most of the test. Sometimes, when both clicks are detected by the computer, the first click selects one link and the second click selects a second link, causing unexpected (i.e., puzzling) results.

Use Open Lists to Select One from Many:
  • Use open lists rather than drop-down lists to select one from many.
  • Generally, the more items users can see in a list (without scrolling), the faster their responses will be, and the fewer omission errors they will make. Ideally, users should be able to see all available items without scrolling.
  • When compared with drop-down lists, open lists tend to elicit faster performance primarily because drop-down lists require an extra click to open. However, if a list is extremely long, a drop-down list may be better. The available research does not indicate the upper number limit of items that should be displayed in a list.

Use Data Entry Fields to Speed Performance:
  • Require users to enter information using data entry fields (instead of selecting from list boxes) if you are designing to speed human performance.
  • At least two studies have compared the effectiveness of text entry versus selection (list boxes) for entering dates and making airline reservations. Both studies found text entry methods were faster and preferred over all other methods. However, use of text entry fields tends to elicit more errors.

Use a Minimum of Two Radio Buttons:
  • Never use one radio button alone.
  • Use at least two radio buttons together. If users can choose not to activate any of the radio button choices, provide a choice labeled 'None.'

Provide Auto-Tabbing Functionality:
  • Provide auto-tabbing functionality for frequent users with advanced Web interaction skills.
  • Auto-tabbing can significantly reduce data entry times for frequent users by not requiring them to manually tab from field to field.

Minimize Use of the Shift Key:
  • Design data entry transactions to minimize use of the Shift key.
  • If possible, designers should not require users to enter characters that require the use the Shift key. Using the Shift key imposes a demand for extra user attention and time. For example, the designer can include symbols such as the dollar or percent sign near data entry fields rather than requiring users to enter those characters. Designers also can treat upper- and lowercases as equivalent when entered by users.


Source:[usability.gov]

Graphics, Images, and Multimedia

0 comments

Graphics are used on many, if not most, Web pages. When used appropriately, graphics can facilitate learning. An important image to show on most pages of a site is the organization's logo. When used appropriately, images, animation, video, and audio can add tremendous value to a Web site. When animation is used appropriately, it is a good idea to introduce the animation before it begins.

Many images require a large number of bytes that can take a long time to download, especially at slower connection speeds. When images must be used, designers should ensure that the graphics do not substantially slow page download times. Thumbnail versions of larger images allow users to preview images without having to download them.

Sometimes it is necessary to label images to help users understand them. Usability testing should be used to help ensure that Web site images convey the intended message. In many cases, the actual data should be included with charts and graphs to facilitate fast and accurate understanding.

It is usually not a good idea to use images as the entire background of a page. Complex background images tend to slow down page loading, and can interfere with reading the foreground text.

Experienced users tend to ignore graphics that they consider to be advertising. Designers should ensure that they do not create images that look like banner ads. Also, they should be careful about placing images in locations that are generally used for advertisements.


Use Simple Background Images:
  • Use background images sparingly and make sure they are simple, especially if they are used behind text.
  • Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates. If background images must be employed, use small, simple images with 'tiling,' and/or keep the image resolution as low as possible.

Label Clickable Images:
  • Ensure that all clickable images are either labeled or readily understood by typical users.
  • Occasional or infrequent users may not use an image enough to understand or remember its meaning. Ensure that images and their associated text are close together so that users can integrate and effectively use them together. Additionally, alt text should accompany every clickable image.

Ensure that Images Do Not Slow Downloads:

  • Take steps to ensure that images on the Web site do not slow page download times unnecessarily.
  • User frustration increases as the length of time spent interacting with a system increases. Users tolerate less delay if they believe the task should be easy for the computer. One study reported that users rated latencies of up to five seconds as ’good.’ Delays over ten seconds were rated as ’poor.’ Users rate pages with long delays as being less interesting and more difficult to scan. One study reported no relationship between slow page download times and users giving up.
  • To speed download times, use several small images rather than a single large image on a page; use interlacing or progressive images; and use several of the same images. Designers should also minimize the number of different colors used in an image and put HEIGHT and WIDTH pixel dimension tags in an image reference. To achieve faster response time for users with dial-up modems, limit page size to less than 30,000 bytes.

Use Video, Animation, and Audio Meaningfully:

  • Use video, animation, and audio only when they help to convey, or are supportive of, the Web site's message or other content.
  • Multimedia elements (such as video, animation, and audio) can easily capture the attention of users; therefore, it is important to have clear and useful reasons for using multimedia to avoid unnecessarily distracting users. Some multimedia elements may take a long time to download, so it is important that they be worth the wait.
  • Used productively, multimedia can add great value to a site's content and help direct users' attention to the most important information and in the order that it is most useful.

Include Logos:

  • Place your organization's logo in a consistent place on every page.
  • Users are frequently unaware when they click through to a different Web site. Having a logo on each page provides a frame of reference throughout a Web site so that users can easily confirm that they have not left the site. Ideally, the logo should be in the same location on each page: many designers place the logo in the top left corner.

Graphics Should Not Look like Banner Ads:

  • Do not make important images look like banner advertisements or gratuitous decorations.
  • In a recent study, a graphic developed to inform users about access to live help was not clicked because many users thought it was an advertisement. Even though the graphic was larger than most other graphics on the page, some users missed the item completely because the graphic looked too much like a decoration or a banner advertisement.

Limit Large Images Above the Fold:

  • Do not fill the entire first screenful with one image if there are screensful of text information below the fold.
  • Large graphics that cover most of the screen at the top of the page suggest to users that there is no more information below the graphic. In one study, because a graphic filled the screen, some users did not use the scrollbar to scroll down to more content. In fact, some users did not even suspect that more information might be located below the fold.

Ensure Web site Images Convey Intended Messages:

  • Ensure that Web site images convey the intended message to users, not just to designers.
  • Users and designers tend to differ in what they think is appropriate to convey a message. When attempting to select the best graphic from a set of graphics, users tend to select those that most other users would have selected (i.e., those that look familiar), while most developers favor graphics that look more artistic. One study found that seventy-five percent of users are able to find information on a content and link-rich site, whereas only seventeen percent could find the same information on a graphic-intensive site.

Limit the Use of Images:
  • Use images only when they are critical to the success of a Web site.
  • Ensure that a Web site’s graphics add value and increase the clarity of the information on the site. Certain graphics can make some Web sites much more interesting for users, and users may be willing to wait a few extra seconds for them to load. Users tend to be most frustrated if they wait several seconds for a graphic to download, and then find that the image does not add any value. Some decorative graphics are acceptable when they do not distract the user.

Include Actual Data with Data Graphics:
  • Include actual data values with graphical displays of data when precise reading of the data is required.
  • Adjacent numeric annotation might be added to the ends of displayed bars on a bar graph, or to mark the points of a plotted curve. Some displays may require complete data annotation while others may require annotation only for selected data elements.

Display Monitoring Information Graphically:
  • Use a graphic format to display data when users must monitor changing data.
  • Whenever possible, the computer should handle data monitoring and should call abnormalities to the users' attention. When that is not possible, and a user must monitor data changes, graphic displays will make it easier for users to detect critical changes and/or values outside the normal range.

Introduce Animation:
  • Provide an introductory explanation for animation prior to it being viewed.
  • Providing an explanation of animation before it begins will help users better integrate the animation and associated content. In other words, briefly explain to users what they are about to see before they see it. Also, allow animation to be user-controlled. The user should be able to pause, stop, replay, or ignore animation or other multimedia elements.

Emulate Real-World Objects:

  • Use images that look like real-world items when appropriate.
  • Images (e.g., pushbuttons and navigation tabs) are likely to be considered as links when they are designed to emulate their real-world analogues. If a designer cannot make such images emulate real-world objects, the image may require at least one additional clickability cue, such as a descriptive label (like 'Home' or 'Next') or placement on the page. A text label can help inform users about a link's destination, but in one study some users missed this type of image link, even those that contained words, because the words were not underlined.

Use Thumbnail Images to Preview Larger Images:

  • When viewing full-size images is not critical, first provide a thumbnail of the image.
  • By providing thumbnails of larger images, users can decide whether they want to wait for the full image to load. By using thumbnails, those who do not need or want to see the full image are not slowed down by large image downloads. Link the thumbnail image to the full-size copy.

Use Images to Facilitate Learning:

  • To facilitate learning, use images rather than text whenever possible.
  • The superiority of pictures over text in a learning situation appears to be strong. For example, pictures of common objects are recognized and recalled better than their textual names. Exceptions seem to occur when the items are conceptually very similar (e.g., all animals or tools), or when items are presented so quickly that learners cannot create verbal labels.

Using Photographs of People:

  • Photographs of people may or may not help build trust in Web sites.
  • In one e-commerce study, having a labeled photograph on the Web site was perceived as more trustworthy than having a photograph with no label. Further, having a photograph with no label was perceived as more trustworthy than having no photograph at all. Highly experienced users showed the same degree of trust as users that were moderately experienced or inexperienced.
  • However, another study recommended that photos not be used to increase the trustworthiness of a Web site. They found that the presence of a photo did not affect the trust of a site, or user preferences for a site.

Source:[usability.gov]

Lists

0 comments

Lists are commonly found on Web sites.These may be lists of, for example, people, drugs, theaters, or restaurants. Each list should be clearly introduced and have a descriptive title. A list should be formatted so that it can be easily scanned. The order of items in the list should be done to maximize user performance, which usually means that the most important items are placed toward the top of the list. If a numbered list is used, start the numbering at 'one,' not 'zero.' Generally only the first letter of the first word is capitalized, unless a word that is usually capitalized is shown in the list.


Order Elements to Maximize User Performance:
  • Arrange lists and tasks in an order that best facilitates efficient and successful user performance.
  • Designers should determine if there is an order for items that will facilitate use of the Web site. If there is, ensure that the site is formatted to support that order, and that all pages follow the same order. For example, ensure that lists of items, sets of links, and a series of tabs are in a meaningful order.
  • Where no obvious order applies, organize lists alphabetically or numerically. Keep in mind that it is the user's logic that should prevail rather than the designer's logic.

Place Important Items at Top of the List:
  • Place a list's most important items at the top.
  • Experienced users usually look first at the top item in a menu or list, and almost always look at one of the top three items before looking at those farther down the list. Research indicates that users tend to stop scanning a list as soon as they see something relevant, thus illustrating the reason to place important items at the beginning of lists.

Format Lists to Ease Scanning:
  • Make lists easy to scan and understand.
  • The use of meaningful labels, effective background colors, borders, and white space allow users to identify a set of items as a discrete list.

Display Related Items in Lists:
  • Display a series of related items in a vertical list rather than as continuous text.
  • A well-organized list format tends to facilitate rapid and accurate scanning. One study indicated that users scan vertical lists more rapidly than horizontal lists. Scanning a horizontal list takes users twenty percent longer than scanning a vertical list.

Introduce Each List:
  • Provide an introductory heading (i.e., word or phrase) at the top of each list.
  • Providing a descriptive heading allows users to readily understand the reason for having a list of items, and how the items relate to each other. The heading helps to inform users how items are categorized, or any prevailing principle or theme. Users are able to use lists better when they include headings.

Use Static Menus:
  • Use static menus to elicit the fastest possible speed when accessing menu items.
  • To elicit the fastest possible human performance, designers should put the most frequently used menus times in the first few positions of a menu. Designers should determine the location of items within a menu based on the frequency of use of each item. Adaptable menus, where users are allowed to change the order of menu items, elicits reasonably fast performance as well. The slowest performance is achieved when an adaptive menu, where the computer automatically changes the position of menu items, is used. One study found that users prefer having static menus, rather than adaptive menus.

Start Numbered Items at One:

  • When items are numbered, start the numbering sequence at 'one' rather than 'zero.'
  • Do not start the numbering with a 'zero.' When counting, people start with 'one,' not 'zero.'

Use Appropriate List Style:
  • Use bullet lists to present items of equal status or value, and numbered lists if a particular order to the items is warranted.
  • Bullet lists work best when the items do not contain an inherent sequence, order, or rank. Numbered lists assign each item in the list an ascending number, making the numerical order readily apparent. Numbered lists are especially important when giving instructions.

Capitalize First Letter of First Word in Lists:
  • Capitalize the first letter of only the first word of a list item, a list box item, check box labels, and radio button labels.
  • Only the first letter of the first word should be capitalized unless the item contains another word that would normally be capitalized.

Source:[usability.gov]

Text Appearance

0 comments

There are several issues related to text characteristics that can help ensure a Web site communicates effectively with users:
  • Use familiar fonts that are at least 12-points;
  • Use black text on plain, high-contrast backgrounds; and
  • Use background colors to help users understand the grouping of related information.
Even though it is important to ensure visual consistency, steps should be taken to emphasize important text. Commonly used headings should be formatted consistently, and attention-attracting features, such as animation, should only be used when appropriate.

Use Black Text on Plain, High-Contrast Backgrounds:
  • When users are expected to rapidly read and understand prose text, use black text on a plain, high-contrast, non-patterned background.
  • Black text on a plain background elicited reliably faster reading performance than on a medium-textured background. When compared to reading light text on a dark background, people read black text on a white background up to thirty-two percent faster. In general, the greater the contrast between the text and background, the easier the text is to read.

Format Common Items Consistently:

  • Ensure that the format of common items is consistent from one page to another.
  • The formatting convention chosen should be familiar to users. For example, telephone numbers should be consistently punctuated (800-555-1212), and time records might be consistently punctuated with colons (HH:MM:SS).

Use Mixed-Case for Prose Text:

  • When users must read a lot of information, use lower-case fonts and appropriate capitalization to ensure the fastest possible reading speed.
  • Using 'mixed-case' fonts for reading prose text means that most letters will be lowercase, with all letters that should be capitalized being in uppercase. Most users have had considerable experience reading lowercase letters and are therefore very proficient at it.

Ensure Visual Consistency:
  • Ensure visual consistency of Web site elements within and between Web pages.
  • Two studies found that the number of errors made using visually inconsistent displays is reliably higher than when using visually consistent displays. Visual consistency includes the size and spacing of characters; the colors used for labels, fonts and backgrounds; and the locations of labels, text and pictures. Earlier studies found that tasks performed on more consistent interfaces resulted in (1) a reduction in task completion times; (2) a reduction in errors; (3) an increase in user satisfaction; and (4) a reduction in learning time.
  • However, users tend to rapidly overcome some types of inconsistencies. For example, one study found that the use of different-sized widgets (such as pushbuttons, entry fields, or list boxes) does not negatively impact users' performance or preferences.

Use Bold Text Sparingly:

  • Use bold text only when it is important to draw the user's attention to a specific piece of information.
  • In the following example with the Field Identifiers bolded on the left, users spent about four times as long looking at the bold Field Identifiers than the non-bold Field Values. In the example on the right, participants spent more time looking at the bolded Field Values. In addition, the non-bold Field Values elicited better search accuracy rates than did the bold Field Values. In situations like this example, it is probably best to not use bold for either field identifiers or field values. In general, bold text should be used sparingly.

Use Attention-Attracting Features when Appropriate:

  • Use attention-attracting features with caution and only when they are highly relevant.
  • Draw attention to specific parts of a Web page with the appropriate (but limited) use of moving or animated objects, size differential between items, images, brightly-colored items, and varying font characteristics.
  • Not all features of a Web site will attract a user's attention equally. The following features are presented in order of the impact they have on users:
  1. Movement (e.g., animation or 'reveals') is the most effective attention-getting item. Research suggests that people cannot stop themselves from initially looking at moving items on a page. However, if the movement is not relevant or useful, it may annoy the user. If movement continues after attracting attention, it may distract from the information on the Web site.
  2. Larger objects, particularly images, will draw users' attention before smaller ones. Users fixate on larger items first, and for longer periods of time. However, users will tend to skip certain kinds of images that they believe to be ads or decoration.
  3. Users look at images for one or two seconds, and then look at the associated text caption. In many situations, reading a text caption to understand the meaning of an image is a last resort. Parts of images or text that have brighter colors seem to gain focus first.
  4. Having some text and graphic items in brighter colors, and others in darker colors, helps users determine the relative importance of elements. Important attention-attracting font characteristics can include all uppercase, bolding, italics, underlining, and increased font size.

Use Familiar Fonts:

  • Use a familiar font to achieve the best possible reading speed.
  • Research shows no reliable differences in reading speed or user preferences for twelve point Times New Roman or Georgia (serif fonts), or Arial, Helvetica, or Verdana (sans serif fonts).

Use at Least 12-Point Font

  • Use at least a 12-point font (e.g., typeface) on all Web pages.
  • Research has shown that fonts smaller than 12 points elicit slower reading performance from users. For users over age 65, it may be better to use at least fourteen-point fonts. Never use less than nine-point font on a Web site.
  • Traditional paper-based font sizes do not translate well to Web site design. For instance, Windows Web browsers display type two to three points larger than the same font displayed on a Macintosh. User-defined browser settings may enlarge or shrink designer-defined font sizes. Defining text size using pixels will result in differently-sized characters depending upon the physical size of the monitor's pixels and its set resolution, and presents accessibility issues to those individuals who must specify large font settings.

Color-Coding and Instructions:

  • When using color-coding on your Web site, be sure that the coding scheme can be quickly and easily understood.
  • One study found that participants were able to answer questions significantly faster when the interface was color-coded, but only when information about the color-coding was provided. When both color-coding and information about how to interpret the colors were provided, user performance improved by forty percent. Be sure that the information provided does not require the user to read and comprehend a lot of text to understand it.

Emphasize Importance:

  • Change the font characteristics to emphasize the importance of a word or short phrase.
  • Font characteristics that are different from the surrounding text will dominate those that are routine. Important font characteristics include bolding, italics, font style (serif vs. sans serif), font size (larger is better to gain attention), and case (upper vs. lower). When used well, text style can draw attention to important words.
  • The use of differing font characteristics has negative consequences as well–reading speed can decrease by almost twenty percent, and thus should be used sparingly in large blocks of prose. Do not use differing font characteristics to show emphasis for more than one or two words or a short phrase. Do not use underlining for emphasis because underlined words on the Web are generally considered to be links.

Highlighting Information:

  • Do not use two (or more) different ways to highlight the same information on one page.
  • One study found that participants were able to complete tasks faster when the interface contained either color-coding or a form of ranking, but not both. The presence of both seemed to present too much information, and reduced the performance advantage by about half.

Source:[usability.gov]

Links

0 comments

Linking means that users will select and click on a hypertext link on a starting page (usually the homepage), which then causes a new page to load. Users continue toward their goal by finding and clicking on subsequent links.

To ensure that links are effectively used, designers should use meaningful link labels (making sure that link names are consistent with their targets), provide consistent clickability cues (avoiding misleading cues), and designate when links have been clicked.

Whenever possible, designers should use text for links rather than graphics. Text links usually provide much better information about the target than do graphics.


Use Meaningful Link Labels:
  • Use link labels and concepts that are meaningful, understandable, and easily differentiated by users rather than designers.
  • To avoid user confusion, use link labels that clearly differentiate one link from another. Users should be able to look at each link and learn something about the link’s destination. Using terms like 'Click Here' can be counterproductive.
  • Clear labeling is especially important as users navigate down through the available links. The more decisions that users are required to make concerning links, the more opportunities they have to make a wrong decision.

Link to Related Content:
  • Provide links to other pages in the Web site with related content.
  • Users expect designers to know their Web sites well enough to provide a full list of options to related content.

Match Link Names with Their Destination Pages:
  • Make the link text consistent with the title or headings on the destination (i.e., target) page.
  • Closely matched links and destination targets help provide the necessary feedback to users that they have reached the intended page.
  • If users will have to click more than once to get to a specific target destination, avoid repeating the exact same link wording over and over because users can be confused if the links at each level are identical or even very similar. In one study, after users clicked on a link entitled 'First Aid,' the next page had three options. One of them was again titled 'First Aid.' The two 'First Aid' links went to different places. Users tended to click on another option on the second page because they thought that they had already reached 'First Aid.'

Avoid Misleading Cues to Click:
  • Ensure that items that are not clickable do not have characteristics that suggest that they are clickable.
  • Symbols usually must be combined with at least one other cue that suggests clickability. In one study, users were observed to click on a major heading with some link characteristics, but the heading was not actually a link.
  • However, to some users bullets and arrows may suggest clickability, even when they contain no other clickability cues (underlining, blue coloration, etc.). This slows users as they debate whether the items are links.

Repeat Important Links:
  • Ensure that important content can be accessed from more than one link.
  • Establishing more than one way to access the same information can help some users find what they need. When certain information is critical to the success of the Web site, provide more than one link to the information. Different users may try different ways to find information, depending on their own interpretations of a problem and the layout of a page. Some users find important links easily when they have a certain label, while others may recognize the link best with an alternative name.

Use Text for Links:
  • Use text links rather than image links.
  • In general, text links are more easily recognized as clickable. Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image.
  • In one study, users showed considerable confusion regarding whether or not certain images were clickable. This was true even for images that contained words. Users could not tell if the images were clickable without placing their cursor over them ('minesweeping'). Requiring users to 'minesweep' to determine what is clickable slows them down.
  • Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

Designate Used Links:
  • Use color changes to indicate to users when a link has been visited.
  • Generally, it is best to use the default text link colors (blue as an unvisited location/link and purple as a visited location/link). Link colors help users understand which parts of a Web site they have visited. In one study, providing this type of feedback was the only variable found to improve the user's speed of finding information. If a user selects one link, and there are other links to the same target, make sure all links to that target change color.
  • One 2003 study indicated a compliance rate of only thirty-three percent for this guideline; a 2002 study showed a compliance rate of thirty-five percent.

Provide Consistent Clickability Cues:
  • Provide sufficient cues to clearly indicate to users that an item is clickable.
  • Users should not be expected to move the cursor around a Web site ('minesweeping') to determine what is clickable. Using the eyes to quickly survey the options is much faster than 'minesweeping.' Similarly, relying on mouseovers to designate links can confuse newer users, and slow all users as they are uncertain about which items are links.
  • Be consistent in your use of underlining, bullets, arrows, and other symbols such that they always indicate clickability or never suggest clickability. For example, using images as both links and as decoration slows users as it forces them to study the image to discern its clickability.
  • Items that are in the top center of the page, or left and right panels have a high probability of being considered links. This is particularly true if the linked element looks like a real-world tab or push button.

Ensure that Embedded Links are Descriptive:
  • When using embedded links, the link text should accurately describe the link's destination.
  • Users tend to ignore the text that surrounds each embedded link; therefore, do not create embedded links that use the surrounding text to add clues about the link's destination.

Use 'Pointing-and-Clicking':
  • 'Pointing-and-clicking,' rather than mousing over, is preferred when selecting menu items from a cascading menu structure.
  • One study found that when compared with the mouseover method, the 'point-and-click' method takes eighteen percent less time, elicits fewer errors, and is preferred by users.

Use Appropriate Text Link Lengths:
  • Make text links long enough to be understood, but short enough to minimize wrapping.
  • A single word text link may not give enough information about the link's destination. A link that is several words may be difficult to read quickly, particularly if it wraps to another line. Generally, it is best if text links do not extend more than one line. However, one study found that when users scan prose text, links of nine to ten words elicit better performance than shorter or longer links. Keep in mind that it is not always possible to control how links will look to all users because browser settings and screen resolutions can vary.

Indicate Internal vs. External Links:
  • Indicate to users when a link will move them to a different location on the same page or to a new page on a different Web site.
  • One study showed that users tend to assume that links will take them to another page within the same Web site. When this assumption is not true, users can become confused. Designers should try to notify users when they are simply moving down a page, or leaving the site altogether.

Clarify Clickable Regions of Images:
  • If any part of an image is clickable, ensure that the entire image is clickable or that the clickable sections are obvious.
  • Users should not be required to use the mouse pointer to discover clickable areas of images. For example, in a map of the United States, if individual states are clickable, sufficient cues should be given to indicate the clickable states.

Link To Supportive Information:
  • Provide links to supportive information.
  • Use links to provide definitions and descriptions to clarify technical concepts or jargon, so that less knowledgeable users can successfully use the Web site. For example, provide links to a dictionary, glossary definitions, and sections dedicated to providing more information.

Source:[usability.gov]

Navigation

0 comments

Navigation refers to the method used to find information within a Web site. A navigation page is used primarily to help users locate and link to destination pages. A Web site's navigation scheme and features should allow users to find and access information effectively and efficiently. When possible, this means designers should keep navigation-only pages short. Designers should include site maps, and provide effective feedback on the user's location within the site.

To facilitate navigation, designers should differentiate and group navigation elements and use appropriate menu types. It is also important to use descriptive tab labels, provide a clickable list of page contents on long pages, and add 'glosses' where they will help users select the correct link. In well-designed sites, users do not get trapped in dead-end pages.

Provide Navigational Options:
  • Do not create or direct users into pages that have no navigational options.
  • Many Web pages contain links that open new browser windows. When these browser windows open, the Back button is disabled (in essence, the new browser window knows nothing of the user's past navigation, and thus is disabled). If the new window opens full-screen, users may not realize that they have been redirected to another window, and may become frustrated because they cannot press Back to return to the previous page. If
  • such links are incorporated into a Web site, the newly-opened window should contain a prominent action control that will close the window and return the user to the original browser window.
  • In addition, designers should not create Web pages that disable the browser's Back button. Disabling the Back button can result in confusion and frustration for users, and drastically inhibits their navigation.

Differentiate and Group Navigation Elements:
  • Clearly differentiate navigation elements from one another, but group and place them in a consistent and easy to find place on each page.
  • Create a common, Web site-wide navigational scheme to help users learn and understand the structure of your Web site. Use the same navigation scheme on all pages by consistently locating tabs, headings, lists, search, site map, etc. Locate critical navigation elements in places that will suggest clickability (e.g., lists of words in the left or right panels are generally assumed to be links).
  • Make navigational elements different enough from one another so that users will be able to understand the difference in their meaning and destination. Grouping reduces the amount of time that users need to locate and identify navigation elements.
  • Do not make users infer the label by studying a few items in the group. Finally, make it easy for users to move from label to label (link to link) with a single eye movement. This best can be done by positioning relevant options close together and to using vertical lists.

Use a Clickable 'List of Contents' on Long Pages:
  • On long pages, provide a 'list of contents' with links that take users to the corresponding content farther down the page.
  • For long pages with several distinct sections that are not visible from the first screenful, add a short, clickable list of the sections (sometimes called 'anchor' or 'within-page' links) at the top of the page. 'Anchor links' can serve two purposes: they provide an outline of the page so users can quickly determine if it contains the desired information, and they allow users to quickly navigate to specific information.
  • Since 'anchor links' enable a direct link to content below the first screenful, they are also useful for getting users to specific information quickly when they arrive from a completely different page.

Provide Feedback on Users' Location:
  • Provide feedback to let users know where they are in the Web site.
  • Feedback provides users with the information they need to understand where they are within the Web site, and for proceeding to the next activity. Examples of feedback include providing path and hierarchy information (i.e., 'breadcrumbs'), matching link text to the destination page's heading, and creating URLs that relate to the user's location on the site. Other forms of feedback include changing the color of a link that has been clicked (suggesting that destination has been visited), and using other visual cues to indicate the active portion of the screen.

Place Primary Navigation Menus in the Left Panel:
  • Place the primary navigation menus in the left panel, and the secondary and tertiary menus together.
  • One study found that navigation times were faster when the primary menu was located in the left panel. Also, navigation performance was best when the secondary and tertiary menus were placed together. Placing a navigation menu in the right panel was supported as a viable design option by both performance and preference measures. Users preferred having the primary menu in the left panel, and grouping secondary and tertiary menus together, or grouping all three menu levels together. The best performance and preference was achieved when all three menus were placed in the left panel (placing them all in the right panel achieved close to the same performance level).

Use Descriptive Tab Labels:
  • Ensure that tab labels are clearly descriptive of their function or destination.
  • Users like tabs when they have labels that are descriptive enough to allow error-free selections. When tab labels cannot be made clear because of the lack of space, do not use tabs.

Present Tabs Effectively:
  • Ensure that navigation tabs are located at the top of the page, and look like clickable versions of real-world tabs.
  • Users can be confused about the use of tabs when they do not look like real-world tabs. Real-world tabs are those that resemble the ones found in a file drawer. One study showed that users are more likely to find and click appropriately on tabs that look like real-world tabs.

Keep Navigation-Only Pages Short:

  • Do not require users to scroll purely navigational pages.
  • Ideally, navigation-only pages should contain no more than one screenful of information. Users should not need to scroll the page, even a small distance. One study showed that users considered the bottom of one screenful as the end of a page, and they did not scroll further to find additional navigational options.

Use Appropriate Menu Types:
  • Use 'sequential' menus for simple forward-moving tasks, and use 'simultaneous' menus for tasks that would otherwise require numerous uses of the Back button.
  • Most Web sites use familiar 'sequential' menus that require items to be selected from a series of menus in some predetermined order. After each selection is made, another menu opens. The final choice is constrained by the sum total of all previous choices.
  • Simultaneous menus display choices from multiple levels in the menu hierarchy, providing users with the ability to make choices from the menu in any order. Simultaneous menus are often presented in frames, and are best employed in situations where users would have to make extensive use of the Back button if presented with a sequential menu.

Use Site Maps:
  • Use site maps for Web sites that have many pages.
  • Site maps provide an overview of the Web site. They may display the hierarchy of the Web site, may be designed to resemble a traditional table of contents, or may be a simple index.
  • Some studies suggest that site maps do not necessarily improve users' mental representations of a Web site. Also, one study reported that if a site map does not reflect users' (or the domain's) conceptual structure, then the utility of the map is lessened.

Use 'Glosses' to Assist Navigation:
  • Provide 'glosses' to help users select correct links.
  • 'Glosses' are short phrases of information that popup when a user places his or her mouse pointer close to a link. It provides a preview to information behind a link. Users prefer the preview information to be located close to the link, but not placed such that it disturbs the primary text.
  • However, designers should not rely on the ’gloss’ to compensate for poorly labeled links.

Breadcrumb Navigation:
  • Do not expect users to use breadcrumbs effectively.
  • One study reported no difference in task completion times and total pages visited between groups that had breadcrumbs and those that did not. Participants could have used breadcrumbs thirty-two percent of the time, but only did so six percent of the time. It is probably not worth the effort to include breadcrumbs unless you can show that your Web site's users use them frequently, either to navigate the site, or to understand the site's hierarchy.
  • One study found that test participants who received instruction on the use of breadcrumbs completed tasks much faster than those who did not. This time savings could result in increased productivity for users that search Web sites on a daily basis.

Source:[usability.gov]

Headings, Titles, and Labels

0 comments

Most users spend a considerable amount of time scanning rather than reading information on Web sites. Well-designed headings help to facilitate both scanning and reading written material. Designers should strive to use unique and descriptive headings, and to use as many headings as necessary to enable users to find what they are looking for-it is usually better to use more rather than fewer headings. Headings should be used in their appropriate HTML order, and it is generally a good idea not to skip heading levels.

Designers should ensure that each page has a unique and descriptive page title. When tables are used, designers should make sure that descriptive row and column headings are included that enable users to clearly understand the information in the table. It is occasionally important to highlight certain critical information.


Use Clear Category Labels:
  • Ensure that category labels, including links, clearly reflect the information and items contained within the category.
  • Category titles must be understood by typical users. Users will likely have difficulty understanding vague, generalized link labels, but will find specific, detailed links, and descriptors easier to use.

Provide Descriptive Page Titles:
  • Put a descriptive, unique, concise, and meaningfully different title on each Web page.
  • Title refers to the text that is in the browser title bar (this is the bar found at the very top of the browser screen). Titles are used by search engines to identify pages. If two or more pages have the same title, they cannot be differentiated by users or the Favorites capability of the browser. If users bookmark a page, they should not have to edit the title to meet the characteristics mentioned above.
  • Remember that some search engines only list the titles in their search results page. Using concise and meaningful titles on all pages can help orient users as they browse a page or scan hot lists and history lists for particular URLs. They can also help others as they compile links to your pages.
  • To avoid confusing users, make the title that appears in the heading of the browser consistent with the title in the content area of the pages.

Use Descriptive Headings Liberally:
  • Use descriptive headings liberally throughout a Web site.
  • Well-written headings are an important tool for helping users scan quickly. Headings should conceptually relate to the information or functions that follow them.
  • Headings should provide strong cues that orient users and inform them about page organization and structure. Headings also help classify information on a page. Each heading should be helpful in finding the desired target.
  • The ability to scan quickly is particularly important for older adults because they tend to stop scanning and start reading more frequently. If headings are not descriptive or plentiful enough, the user may start reading in places that do not offer the information they are seeking, thereby slowing them down unnecessarily.

Use Unique and Descriptive Headings:
  • Use headings that are unique from one another and conceptually related to the content they describe.
  • Using poor headings (mismatches between what users were expecting and what they find) is a common problem with Web sites. Ensure that headings are descriptive and relate to the content they introduce.
  • If headings are too similar to one another, users may have to hesitate and re-read to decipher the difference. Identifying the best headings may require extensive usability testing and other methods.

Highlight Critical Data:
  • Visually distinguish (i.e., highlight) important page items that require user attention, particularly when those items are displayed infrequently.
  • Items to highlight might include recently changed data, data exceeding acceptable limits, or data failing to meet some other defined criteria. Highlight is used here in its general sense, meaning to emphasize or make prominent. Highlighting is most effective when used sparingly, i.e., highlighting just a few items on a page that is otherwise relatively uniform in appearance.

Use Descriptive Row and Column Headings:
  • Ensure that data tables have clear, concise, and accurate row and column headings.
  • Use row and column headings to indicate unique cell contents. Users require clear and concise table headings in order to make efficient and effective use of table information. Row and column headings will indicate to screen readers how data points should be labeled or identified, so the user can understand the significance of the cell in the overall scheme of the table.

Use Headings in the Appropriate HTML Order:
  • Use headings in the appropriate HTML order.
  • Using the appropriate HTML heading order helps users get a sense of the hierarchy of information on the page. The appropriate use of H1-H3 heading tags also allows users of assistive technologies to understand the hierarchy of information.

Provide Users with Good Ways to Reduce Options:
  • Provide users with good ways to reduce their available options as efficiently as possible.
  • Users seem willing to reduce their options quickly. Provide all options clearly so that users can focus first on selecting what they consider to be the most important option.

Source:[usability.gov]

Scrolling and Paging

0 comments

Designers must decide, early in the design process,whether to create long pages that require extensive scrolling or shorter pages that will require users to move frequently from page to page (an activity referred to as paging). This decision will be based on considerations of the primary users and the type of tasks being performed. For example, older users tend to scroll more slowly than younger users; therefore, long scrolling pages may slow them down considerably. As another example, some tasks that require users to remember where information is located on a page may benefit from paging, while many reading tasks benefit from scrolling.

Generally, designers should ensure that users can move from page to page as efficiently as possible. If designers are unable to decide between paging and scrolling, it is usually better to provide several shorter pages rather than one or two longer pages. The findings of usability testing should help confirm or negate that decision.

When scrolling is used, a Web site should be designed to allow the fastest possible scrolling. Users only should have to scroll through a few screenfuls, and not lengthy pages. Designers should never require users to scroll horizontally.


Use Scrolling Pages For Reading:
  • Use an appropriate page layout to eliminate the need for users to scroll horizontally.
  • Horizontal scrolling is a slow and tedious way to view an entire screen. Common page layouts including fluid and left-justified may require some users to scroll horizontally if their monitor resolution or size is smaller than that used by designers.

Facilitate Rapid Scrolling While Reading:
  • Facilitate fast scrolling by highlighting major items.
  • Web pages will move quickly or slowly depending on how users elect to scroll. Some users click on the arrows at the ends of the scroll bar, which can be slow but does allow most information to be read during the scrolling process. Other users drag the scroll box, which tends to be much faster. When the scroll box is dragged, the information may move too fast on the screen for users to read prose text, but they can read major headings that are well-designed and clearly placed. Keep in mind that older users (70 and over) will scroll much more slowly than younger users (39 and younger).

Use Scrolling Pages For Reading Comprehension:
  • Use longer, scrolling pages when users are reading for comprehension.
  • Make the trade-off between paging and scrolling by taking into consideration that retrieving new linked pages introduces a delay that can interrupt users’ thought processes. Scrolling allows readers to advance in the text without losing the context of the message as may occur when they are required to follow links.
  • However, with pages that have fast loading times, there is no reliable difference between scrolling and paging when people are reading for comprehension. For example, one study showed that paging participants construct better mental representations of the text as a whole, and are better at remembering the main ideas and later locating relevant information on a page. In one study, paging was preferred by inexperienced users.

Use Paging Rather Than Scrolling:
  • If users' system response times are reasonably fast, use paging rather than scrolling.
  • Users should be able to move from page to page by selecting links and without having to scroll to find important information.

Scroll Fewer Screenfuls:
  • If users are looking for specific information, break up the information into smaller portions (shorter pages).
  • For many Web sites, users deal best with smaller, well-organized pages of information rather than lengthy pages because scrolling can take a lot of time. Older users tend to scroll much more slowly than younger users. One study found that Internet users spend about thirteen percent of their time scrolling within pages. Even though each event takes little time, cumulative scrolling adds significant time.


Source:[usability.gov]