RE: How long should an onscreen message last?

["GeneK" <gene -at- genek -dot- com>]

I think a visit to your local ATM machine with a stopwatch
is in order.  I've never timed my local ATM, but I'm 
guessing that your 5 secs is about right.  But is the 
onscreen message the only return, or is there an audio 
cue?  I think most people by now are accustomed to the 
little chirps that accompany ATM key strokes, the fast 
beeps that announce the machine is awaiting input, and the 
nasty little buzz that accompanies the "bad input" message 
(which, btw, usually says something more along the lines 
of "invalid input, try again," "ACCESS DENIED" being more 
appropriate for the self-destruct console of the Starship 
Enterprise).  

Gene Kim-Eng

------- Original Message -------
On
Tue, 24 Jun 2003 10:47:36 -0700 Chris Knight?wrote:


Here's my hypothesis:
First, better not wait longer than 10 seconds to dismiss the "ACCESS DENIED"
message.
But I'm thinking *5 seconds* should be long enough, while the disappointed
party (who couldn't connect with that other party) stares at the screen, and
slowly, scratching his head, and without vandalizing the system, leaves the
front of the panel ... for the next person. No more than 10 seconds, though.

I will test and report.
Comments?
Anyone have any relevant research?


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ANNOUNCING ROBOHELP STUDIO

RoboHelp Studio maximizes your Help authoring power by combining 
RoboHelp Office and RoboDemo, so you can easily create professional 
Help systems that feature interactive tutorials and demos.

Find out more about RoboHelp Studio at http://www.ehelp.com/techwr-l2

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.