TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I have to agree with Geoff that Cancel gives me a comfort level --
especially when using software for the first time. I like to play around and
discover all the dialog boxes and without a cancel button, I wouldn't feel
good about it.
But instead of "Yes" and "No" I prefer "OK" and "Cancel", or "[Command]" and
"Cancel". e.g., if it is a Save box, then "Save" and "Cancel" or if it is
the Eat Muppets box, then "Eat Muppets" and "Cancel".
From: Geoff Hart [mailto:Geoff-h -at- mtl -dot- feric -dot- ca]
Sent: Thursday, April 22, 1999 11:11 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Standard cancel buttons?
John Posada wondered <<In most applications, when you
issue a command that generates a dialog box with [yes] or
[no] buttons, is it customary to also include a [cancel] button
or is this on a case-by-case basis?>>
I have absolutely no usability data to support this, but
personally, I hate dialog boxes without a "cancel" button, and
the more so when the dialog info. really isn't written so that
"yes" and "no" are the correct answers to the question. If
nothing else, "cancel" lets me say "damn... I'm really not sure
this will do what I want it to; let me click cancel, open the
help file, and try again if I'm really sure". Sometimes a yes or
no simply doesn't tell me this, and I have to leap into oblivion
trusting my instincts and remembering those times I've been