E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: Karin Carlson
Date: Wed, Jun 19 2019 2:35PM
Subject: Protocol when writing app instructions
No previous message | Next message →

Hello, everyone.

As an instructional designer with experience working on content for
Microsoft, I've been using the Microsoft style guide wordings when writing
instructions that describe doing something in an application. For example,
you click a link or menu, but select a checkbox. Recently, a colleague of
mine told me that, to be compliant with accessibility standards, we should
stop using "click" for any instruction (because it's mouse-centric), and
use "select" instead. So, "click the link" would change to "select the
link" (To be clear, I'm not talking about JS events, this is just written
instructions, as you would find in a learning job aid or quick reference.)

To me this is 100% wrong, because a) it doesn't map to Microsoft (and
other) manual of style; 2) it doesn't describe what you are doing (and I
personally believe that everyone, sighted or not, understands what
"clicking" a button is, and "selecting" is a different action); and 3)
inconsistency is generally not good for UX or for accessibility.

1 - Does anyone know of a reliable resource (like W3C) that has written on
this topic? I can't find anything.
2 - Does anyone have personal experience with testing instruction-type
material where this has come up?

Thanks

Karin
Karin Carlson, MCT, MSOMS
Accessibility Consultant/Trainer
instructional Designer
Applications Instructor

From: Steve Green
Date: Wed, Jun 19 2019 2:48PM
Subject: Re: Protocol when writing app instructions
← Previous message | Next message →

Our report writing guidelines say to use the word "operate" for links and buttons rather than "click" because it is independent of the mode of operation, such as clicking, tapping, keyboard operation or voice control. I agree that "select" is definitely not appropriate.

Steve Green
Managing Director
Test Partners Ltd

From: Aditya
Date: Wed, Jun 19 2019 5:39PM
Subject: Re: Protocol when writing app instructions
← Previous message | Next message →

Similar to "operate" being equivalent to a click/tap, what would be the recommended instruction for executing swipe for a voice over user on iPhone or iPad?

Sent from my iPhone

> On Jun 19, 2019, at 3:48 PM, Steve Green < = EMAIL ADDRESS REMOVED = > wrote:
>
> Our report writing guidelines say to use the word "operate" for links and buttons rather than "click" because it is independent of the mode of operation, such as clicking, tapping, keyboard operation or voice control. I agree that "select" is definitely not appropriate.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>
>

From: Steve Green
Date: Thu, Jun 20 2019 4:52AM
Subject: Re: Protocol when writing app instructions
← Previous message | Next message →

It depends on the purpose of the swipe. Bear in mind that Voiceover users on mobile devices may be using a keyboard for input and control as well as or instead of the touchscreen.

Steve

From: Jim Homme
Date: Thu, Jun 20 2019 10:21AM
Subject: Re: Protocol when writing app instructions
← Previous message | Next message →

Hi,
I'm pretty sure that if you want a swipe to get from VoiceOver to an app that this will not happen unless the user employs a special gesture on VoiceOver. This is because VoiceOver uses swipes for its own purposes. If there is a way to do the same thing in the app with a tap gesture, that will always work.

Thanks.

Jim



=========Jim Homme
Digital Accessibility
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions

From: Aditya
Date: Thu, Jun 20 2019 10:32AM
Subject: Re: Protocol when writing app instructions
← Previous message | Next message →

Yes, there is a way to swipe using voiceover - double tap and hold, and swipe - This is equivalent to swiping on an element.

But would you say "swipe" in the instruction or something else.?
Like, would you say "tap to select" or "double tap to select" as an instruction for screen reader user?
If it's the former, we can say "swipe for next".


Sent from my iPhone

> On Jun 20, 2019, at 11:21 AM, Jim Homme < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi,
> I'm pretty sure that if you want a swipe to get from VoiceOver to an app that this will not happen unless the user employs a special gesture on VoiceOver. This is because VoiceOver uses swipes for its own purposes. If there is a way to do the same thing in the app with a tap gesture, that will always work.
>
> Thanks.
>
> Jim
>
>
>
> =========> Jim Homme
> Digital Accessibility
> Bender Consulting Services
> 412-787-8567
> https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
>
>

From: Jim Homme
Date: Thu, Jun 20 2019 10:38AM
Subject: Re: Protocol when writing app instructions
← Previous message | No next message

Hi,
If the instructions are specifically for VoiceOver users, I would tell them to double tap then hold, then swipe. I would not assume that they know the pass through gesture.

Jim



=========Jim Homme
Digital Accessibility
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions