This page is a draft


The user needs to perform an action on the data entered in a form, such as submitting a query, or saving or previewing their content.


Single button

[img, TBA]

Multiple buttons

[img, TBA]

The primary goal of Web form design is to get people through a form quickly and painlessly. Where possible, create forms for a single purpose and provide a single button to complete that task.

Sometimes, however, forms will require additional, secondary actions, such as 'preview' as an alternative to 'save'. In such cases, visual distinctions are a useful method for helping people make good choices. The most important distinction is between the the primary submit button and any secondary buttons (the 'primary' submit button is the submit button that is essential to the form, and which fulfills its primary purpose). Therefore, in multi-button forms, the primary form button should be visually emphasized. For consistency, single-button forms should also visually emphasize their submit button.

HowTo: Taming the form buttons

Note: The following tutorial assumes that your are developing your own module and that you have at least a passing familiarity with Drupal's Form API.

Buttons Up and Down

In most cases and environments, form buttons remain the most elegant and practical way for a user to interact quickly with the data that is displayed in a browser window. Drupal's Form API provides three (3) types of buttons: submit, button and image_button.

Subscribe with RSS Subscribe to RSS - button