Buttons

							Buttons




Fig 1: the last item on the page is the preferred action, and submits the data


Information Architecture
 Use Buttons to initiate data submission and confirmation on most data entry forms. Avoid placing more than two
      buttons on a page.
 Do not use Buttons for navigational functions such as Start Process or Return to Beginning.

Interaction Design
 In common forms, avoid using Buttons for Cancel; use a Cancel link instead (see Cancel link). In general, do not
       provide Reset or Clear buttons in forms.
 Do not use a button at the bottom of a Child window or Layer. Close Child windows and Layers by using the special
       Close icon button in the upper right corner, instead of a button

Visual Design
 Place buttons under tables and forms at the bottom right.
 If there is more than one button applicable to a form or a page in a process, place the button with the preferred
        action (“Next” or “Submit”) as the right-most button, so that the last action on the page is the one that
        advances the user forward

Editorial
 Use one or two words as button names to keep Buttons small.
 Use these common Button names, as applicable:
    - Submit: Use to commit data for processing, with the expectation that a confirmation will appear.
    - Save: Use to update data on pages such as "Preferences" and "Settings," when the action isn't necessarily going
          to navigate the user to another page.
    - < Previous and Next >: Use these buttons on pages that are part of a multi-page flow. Do not use "Next >" to
          initiate the final data submission. Make sure that the button on the final page clearly indicates that data will
          be saved or submitted.
    - Calculate: Use to initiate processing that requires some type of calculation.
    - Search: Use to initiate a search for information.