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: How to write for both mouse and touch screen From:"Bowes, Rebecca" <Rebecca-Bowes -at- IDEXX -dot- com> To:"Weissman, Jessica" <WeissmanJ -at- abacustech -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 20 Dec 2013 22:19:03 +0000
Thanks, Jessica. My first instinct was to continue to use "click," but I'm afraid I may be giving the new touch-screen capability short shrift if I do that. Hence the difficulty! I'm glad to know that you think it's a viable option, though. It will be interesting to see if others think so, too.
From: Weissman, Jessica [mailto:WeissmanJ -at- abacustech -dot- com]
Sent: Friday, December 20, 2013 5:01 PM
To: Bowes, Rebecca; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: How to write for both mouse and touch screen
It's a tough issue.
I'd just say "click", on the grounds that if people can manage to hit buttons on a phone and talk about it as "dialing" a number, they can tap something if told to click it.
"Select" has a slightly different meaning. When I was documenting UIs I used "select" for picking something out of all the things you could pick, and "click" for taking action on something. Our users "select"ed one of the options, then clicked OK to make it happen. Or they "selected" a category. Sometimes a selection took effect immediately; a click always did.
I'm fully aware that this is an imperfect and moderately inconsistent solution. But it worked. Users we tested our UI on had little trouble with it.
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.