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.
Many windows-based software applications provide at least two ways of doing
things, one by keyboarding, one by point-and-click. To be thorough,
accurate, and address the needs of users who prefer one method over the
other, the Technical Communicator should be documenting mouse and keyboard
procedures, if both exist.
Another example: If you are documenting an application for users who are not
Windows literate, you may also need to be very specific about when to use
the mouse, and when to use the keyboard. I have a large sector of users who
have only mainframe green screen orientation. Many of them don't have
computers at home. Try explaining how to scroll in a browser to somebody
who's never used a mouse-but who understands the concept of cursor, tab key
and enter key. These are not stupid people, just people who have been used
to doing things in the mainframe world for a long time. Audience analysis
and usability testing can bring these issues to light, but it's a shorter
production cycle if you know that up front.
MTC
Connie Giordano
-----Original Message-----
From: Barb Einarsen [mailto:barb -dot- einarsen -at- gnnettest -dot- com]
Sent: Thursday, May 25, 2000 2:17 PM
To: TECHWR-L
Subject: Re: terminology question: pointer vs. cursor
How about pointer vs. cursor vs. nothing. I pick nothing. Why do you need to
discuss the mouse or keyboard in either manner? What, pray-tell, are you
documenting?
