Here's an interesting documentation-related discussion happening on another email list I subscribe to. I know that we have a lot of "click on X" language in our docs. Should we consider some other term that also includes tapping, hitting Enter, voice control, etc.?
---------- Forwarded message --------- From: Aditya via WebAIM-Forum <[email protected]> Date: Wed, Jun 19, 2019 at 4:39 PM Subject: Re: [WebAIM] Protocol when writing app instructions To: WebAIM Discussion List <[email protected]> Cc: Aditya <[email protected]> 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 protected]> > 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 protected]> On Behalf Of Karin > Carlson > Sent: 19 June 2019 21:35 > To: [email protected] > 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 > _______________________________________________ > To manage your subscription, visit http://list.webaim.org/ List archives at > http://webaim.org/discussion/archives > Address list messages to [email protected] > _______________________________________________ > To manage your subscription, visit http://list.webaim.org/ > List archives at http://webaim.org/discussion/archives > Address list messages to [email protected] _______________________________________________ To manage your subscription, visit http://list.webaim.org/ List archives at http://webaim.org/discussion/archives Address list messages to [email protected] -- Jane Sandberg Electronic Resources Librarian Linn-Benton Community College [email protected] / 541-917-4655 Pronouns: she/her/hers _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
