Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Comments on mice don't tap and tablet-users don't click: what word can I use for all audiences instead?

Parent

mice don't tap and tablet-users don't click: what word can I use for all audiences instead?

+7
−0

I am documenting features on a web site. The audience is end users, who could be anywhere from seasoned Internet veterans to relatively new people who came for my site's content but aren't generally online for hours every day. People visit the web site on a variety of devices, from phones (mobile site, touch) to tablets (desktop site, touch) to traditional computers (desktop site, mouse), and we do not plan to make documentation variants per form factor. (The site itself is responsive and follows mobile and desktop conventions as applicable.)

The documentation style is imperative, not descriptive (for clarity and to follow widespread convention). Sometimes the documentation needs to tell the user to interact with a button or link. Before mobile, we would have said "click". People reading on mobile devices know to mentally translate "click" to "tap" when reading instructions, but it makes me wonder if they are, in the back of their minds, wondering whether mobile is an afterthought for us and what else might be wrong in our documentation, so if I can find a better term I'd like to.

I considered "select", but to experienced techies that means "highlight", not "invoke". I don't know how much I should be concerned about that when writing for a general audience. (Most of my previous work has been for very technical readers and must be precise.)

Is there a general-purpose, concise term that works in imperative voice for "invoke a thing in a UI"?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (2 comments)
Post
+1
−1

Click is really the correct term. I know it is a made-up action description for a mouse or trackball. It requires on-the-fly mental replacement with tap when used with a touch-screen (phone, tablet or larger). But click is the term used, for better or worse, within the code that runs all these wonderful web sites. Specifically, it is the onclick event in all modern browsers. In other places, such as this Windows documentation, the events are "button down" and "button up" but the discussion nearly universally speaks about the "click" actions.

As far as alternatives, select is not a great option (pun intended, of course). The reason is that "select" has not one but two very specific meanings already:

  • the HTML select element which contains option elements and is used to select one of many items - for this you can write things like "select a widget from the list"
  • selecting (aka highlighting) text on a page (e.g., "Select All") - for this you can write things like "select text in the box that you want to move and click cut"

Using select in a more general sense dilutes the meaning of select in those two primary uses and can both confuse regular users and annoy advanced users (especially programmers).

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (3 comments)
General comments
Mark Baker‭ wrote over 4 years ago

The language that the code speaks to the machine really has no bearing on the language that the documentation speaks to the user. The machine must be addressed in terms that the machine understands. The user must be addressed in terms that the user understands. They are often very different terms.

manassehkatz‭ wrote over 4 years ago

That is true in some cases. But in this case, I suspect (no proof, no time to research) that the "click" terminology may have actually started with the user side (mice were around before web browsers) and became entrenched enough, including the term getting into Javascript, APIs, etc. that now it is established at both the user and code level - and therefore both not easy to change (but not impossible) and well understood by typical users.

Mark Baker‭ wrote over 4 years ago

I don't disagree with that. Users are familiar with the term click and familiar terms are incredibly persistent. (Horsepower, for instance!) Select and click are both viable options, IMHO. Trying to come up with some exotic new term is the fatal mistake. But we need to make the argument for the right reasons.