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.
Subject:RE: Click X, or click the X button? From:"Combs, Richard" <richard -dot- combs -at- Polycom -dot- com> To:"techwr-l List" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 22 Oct 2009 15:14:20 -0600
Keith Hood wrote:
> My rationale: there may be more than one control visible labeled "X" -
I've
> seen that on poorly designed UIs. So the user may have times when
there is
> an X button and an X menu. The explicitness of "click on the X button"
> tells the user exactly what to look for. If you just write "click X,"
there
> will be users who will think, "the X what?" Some users will have that
> problem even if there aren't redundant control labels. Also (minor
quibble
> time), the mouse button is what you're actually touching, so you you
click
> the mouse button, but you click when the pointer is *on* the screen
> control.
Know your audience, I suppose. Many years ago, when mice were new, maybe
some audiences needed extremely detailed instructions: "Move the mouse
on its pad until the pointer on the screen is over the rectangular
button with the word XYZ on it. Then quickly depress and release the
left button on the mouse once, producing a clicking sound."
Later, for most audiences, the instruction "click the X button" was
sufficiently clear that further elaboration was simply distracting and
annoying wordiness. Not to mention condescending.
Today, for most audiences (and in most semi-decent UIs), anything more
than "click X" is neither necessary nor helpful.
But that's for most audiences. Know your audience ...
Robert Lauriston wrote:
> You include a screen capture for every button? Even Save and Next?
> Cropped to the button, whole dialog, or what?
>
> To me, that's tech-writer busywork that leads to bloated docs and
> slows down readers. I do that only when the UI is bad and it's clear
> that the user will have trouble finding the UI element.
Couldn't agree more.
For most audiences, of course ...
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-