The Importance Of Interface Text (part 2) - Playing The Field (
Page 4 of 8 )
The user has now reached the correct screen, safe in the knowledge that
(s)he will be able to perform the intended task. The continuation of this
feeling depends on how familiar the data requirements on the form seem.
A lot of this has to do with the structuring of the form - the bunching
together of parameters and the manner in which the interdependencies are
depicted. A lot also depends on how familiar the words sound to the user.
Stick to using terms the user is familiar with, and you can't go wrong.
The main function of the field label is to indicate the data requirement of
the field. This should be short, a maximum of three words (and even that's
stretching it!) If it takes you more than three words to explain what a
field does, you need to reconsider the focus of that field.
Button labels need to indicate the "impending action" - that is, what the
effect of clicking them will be. Here's a list of the verbs used for most
of the common actions - most users are familiar with these and what they
represent:
- Submit
- OK
- Cancel
- Reset
- Confirm
- Save
- Delete
- Edit
The important thing, of course, is to use these appropriately and
consistently. It also impacts your screen design - design screens so that
if at one screen you need to "save" information, you do not need to shift
to "confirm" for another one.
/ 3 
