E-mail List Archives
Re: Verbiage for button and link interactions
From: JP Jamous
Date: Dec 16, 2016 7:09AM
- Next message: Aaron Cannon: "Re: Verbiage for button and link interactions"
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: Verbiage for button and link interactions"
- Next message in Thread: Aaron Cannon: "Re: Verbiage for button and link interactions"
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: Verbiage for button and link interactions"
- View all messages in this Thread
How about Execute? The user will figure out whether to tap or click or hit enter. I use that term very often.
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Christopher Myers
Sent: Friday, December 16, 2016 8:02 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Verbiage for button and link interactions
Hi!
I'm passing along a question for a colleague --
They're working on documentation for an online process, and are trying to figure out how to best phrase the interaction that users do with links and buttons.
Some of their coworkers say that it should be "click," but others say it should be "tap." Their reasoning behind "tap" is for mobile devices and accessibility programs. But other users would be confused by "tap" when they're using a pointing device with buttons.
So, I was just curious if there's a "universal" way of referring to one's interactions with "pressable" objects?
Thanks!
Chris
- Next message: Aaron Cannon: "Re: Verbiage for button and link interactions"
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: Verbiage for button and link interactions"
- Next message in Thread: Aaron Cannon: "Re: Verbiage for button and link interactions"
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: Verbiage for button and link interactions"
- View all messages in this Thread