Terminology for both desktops and tablets

Jul 09, 2013

I'm working on a Storyline project that users will be accessing both on desktop PCs and tablets. We're having some disagreement about navigational language, specifically, "Click Next to continue." Since tablet users don't have a mouse to click, this doesn't seem appropriate. On the other hand, "tap" doesn't work for mousers. One person had read something about using "select" as a generic term but to me "select" means choosing from several options and it's confusing to use it in another context.

I couldn't find any online resources addressing this issue. Has anyone here encountered this issue? How did you solve it? We've had WAY too much conversation on this point!

Thanks in advance for your help!

13 Replies

Alexandros Anoyatis

almost 11 years ago07/09/13 at 11:44 am (UTC)

Hi judy,

I usually choose to use a text variable in this scenario.

Something similar to "%select% here to do continue" usually does it.

I then insert a trigger or two to change the value of the 'select' variable to either "click" or "tap" depending on the device the module is being viewed from (usually done via JS).

Hope this helps,
Alex

Judi Gronseth
Author

almost 11 years ago07/09/13 at 1:05 pm (UTC)

That's a great suggestion, Alexandros. We'll try that one. Thanks!

Phil Mayor
Hero

almost 11 years ago07/09/13 at 11:39 pm (UTC)

I like Alex's solution, honestly most users would understand click, tablets are still new and shiny and old terminology still stands.

Most of my navigation instructions are in the audio anyway.

Samuel Bishop

almost 11 years ago07/11/13 at 4:10 pm (UTC)

I have had the same problem, myself. I maintain a troubleshooting knowledge base for tablets, smartphones and laptops. After playing with the words Click, Select, Choose, Go to, Tap, Press - we've settled on Go to and Click as universal terms, and there's been no outrage

Steve Flowers

almost 11 years ago07/12/13 at 6:06 am (UTC)

I've seen arguments on the internet (yes, it does happen). In some UX circles, "Press" is the preferred term. I have taken on the habit to use select since this term could still apply to someone that doesn't have the faculties to press. Select still works in voice commands, etc.. I don't think our audiences care as much about the stuff we argue about as we do

Alexandros Anoyatis

almost 11 years ago07/12/13 at 6:44 am (UTC)

Steve Flowers said:

I've seen arguments on the internet (yes, it does happen). In some UX circles, "Press" is the preferred term. I have taken on the habit to use select since this term could still apply to someone that doesn't have the faculties to press. Select still works in voice commands, etc.. I don't think our audiences care as much about the stuff we argue about as we do

Alex

OWEN HOLT
Hero

almost 11 years ago07/12/13 at 7:19 am (UTC)

I've used the assumption that adults can choose what is appropriate for their needs and include both.

"Click or tap the next button to continue"

No need to limit adults to just a single action.

Ray Handley

over 10 years ago11/04/13 at 5:53 pm (UTC)

Select works fine for us. It can take on a global meaning. Most users understand this to mean click if they are on a PC or Tap/Press if on a mobile device.

Joshua Roberts

over 10 years ago11/05/13 at 12:46 am (UTC)

We've recently changed the terminology that we use now that we're producing content for mobiles/tablets. 'Select' is the most universal term that gives the minimal amount of fuss or confusion.

Kelly Prince

over 10 years ago11/05/13 at 10:52 am (UTC)

I love this discussion and timely as I build my next course which will be accessed on both laptops and tablets. Thanks for all the insight!

Tyson Priddle

over 10 years ago11/05/13 at 5:02 pm (UTC)

It's an interesting discussion this one, and one I've thrown up on a few recent projects.

My goal on my next project is to review the need for any instructional text, by using clever design/instructional strategy - which makes it blatantly obvious what the next step is.

The context of this would obviously change, however for example do we really need to add "Click the forward arrow to continue" if there is a great big forward arrow staring learners in the face? I'd like to give my learners a bit more credit...

Bruce Graham
Hero

over 10 years ago11/06/13 at 1:28 am (UTC)

As I often say to clients - I think out users understand what we mean a high % of the time.

These are people that will Pause a course, then go and maybe make a microwave lunch, call someone on their iPhone, and do some photocopying. They do not need instructions for any of those, (have you ever really read the instructions to a photocopier?).

As all of those are about x14 harder than navigating any of the courses we build, I think they'll be able to figure it out most of the time if we are as clear as we can be. Saying that, a clean set of instructions is always best, refer to "big arrows", or "numbered buttons" or whatever.