E-mail List Archives
Re: Protocol when writing app instructions
From: Aditya
Date: Jun 19, 2019 5:39PM
- Next message: Aditya: "Re: Best way to prevent screen reader reading aria-live region in browse mode?"
- Previous message: Steve Green: "Re: Protocol when writing app instructions"
- Next message in Thread: Steve Green: "Re: Protocol when writing app instructions"
- Previous message in Thread: Steve Green: "Re: Protocol when writing app instructions"
- View all messages in this Thread
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 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
>
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Karin Carlson
> Sent: 19 June 2019 21:35
> To: <EMAIL REMOVED>
> Subject: [WebAIM] Protocol when writing app instructions
>
> 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
> > > > > > >
- Next message: Aditya: "Re: Best way to prevent screen reader reading aria-live region in browse mode?"
- Previous message: Steve Green: "Re: Protocol when writing app instructions"
- Next message in Thread: Steve Green: "Re: Protocol when writing app instructions"
- Previous message in Thread: Steve Green: "Re: Protocol when writing app instructions"
- View all messages in this Thread