Re: MATF Minutes November 7, 2019

Started with an update for 2.2 SC Instructions for Custom Interactions.

Would love to see feedback so far before continuation.


  1.  The idea is that if you can use a standard interaction you're fine, always.
  2.  The moment you start combining standard interactions OR 'add' multiple functions underneath a standard interaction it becomes custom and you need to provide instructions.
  3.  The instruction can be a visual indicator OR an explanation somewhere / somehow

https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit

Cheers,
Jake
________________________________
From: Kim Patch <kim@redstartsystems.com>
Sent: Thursday, November 7, 2019 6:31 PM
To: public-mobile-a11y-tf@w3.org <public-mobile-a11y-tf@w3.org>
Subject: MATF Minutes November 7, 2019

MATF Minutes November 7, 2019

Link: https://www.w3.org/2019/11/07-mobile-a11y-minutes.html

Text:

Mobile Accessibility Task Force Teleconference
07 Nov 2019
Attendees

Present
Kim, Jake
Regrets

Chair
Kimberly_Patch
Scribe
Kim
Contents

  *   Topics<https://www.w3.org/2019/11/07-mobile-a11y-minutes.html#agenda>
  *   Summary of Action Items<https://www.w3.org/2019/11/07-mobile-a11y-minutes.html#ActionSummary>
  *   Summary of Resolutions<https://www.w3.org/2019/11/07-mobile-a11y-minutes.html#ResolutionSummary>

________________________________

https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit

Custom Interactions

https://docs.google.com/document/d/13QWLthBoEU6xuJQ4UrYOwuvJp0a42Z70JRjAsjtv1m4/edit?usp=sharing

Kim: good to have examples when we are talking about it

Jake: hard to draw the line – what are custom gestures. Also placement and timing
... custom gestures – two different kinds of gestures, Drag and one with the intermediate point. If we plot that to what we want to solve and we don't want to make it too complicated by saying you need to know all your gestures – Apple iOS android and whatever. Or even the question about why area. If we approach it from another angle and say that If you use a standard gesture or key or interaction – when you use a regular swipe left, etc.

If there are more possibilities than just the one regular swipe left, other types of swipes left, you have to provide help

Jake: so we want to cover the ones where there are more than one left swipes available, or more than one gestures or keys that work together, like going left and going up instead of only left or only up for only double tap. So the moment it gets complicated by combining two, and it doesn't matter if it's too gestures combining three or four or two actions beneath the gesture or three or four, at that moment you have to provide help

https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6?usp=sharing

RESOURCE FROM jAKE https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6

Jake: we could create a standard list – Example above page 5, 6, etc. If it's a standard gesture
... good, but if you have to combine or if there's not a clue – feedback for what happened, you need to explain
... these are the gestures, if there is no official hand like an arrow right or down and suddenly there's an action beneath it then you need to explain it. If there's more than one action then you still need to explain it because there are more then one actions possible, and if it's combining gestures you also need to provide help. And this is the list of gestures, list of default keystrokes etc.
... so combining two keys makes it custom as well
... if we go directly to why area and the question – are those custom interactions if they just work in the same way with the default arrow and you don't have to combine them, no, but the moment you have to hold one key together with another then yes you have to provide help
... but I'd like to do with the keyboard is if you can interact with the arrow and, fine, and Maybe the escape key, but everything else is a custom one, including Key shortcuts, need to be documented.
... so everything else has to be documented – so that seems like an easy one
... so in that case it's about whether it works with the tab or arrows in that case you're covered
... so it kicks in when you need to press two keys
... arrow, tab and one key combination to open an instruction file
... I think we need to make a list of gestures. Single tap, double tap, swipe four directions, flick– we need to agree on the set as we did with input purpose
... and then combining any of them need help. And then If you have a single gesture with Affordance – feedback, fine, but if you have a single gesture without a clue of what will happen you also need help.

example Netflix – if you only see two movies and you have no idea that there's a third if you swipe left right, you also need to provide something – feedback or instructions

Kim: feedback is instruction – this is a good way to put it

Jake: if you have feedback it's very clear, so you don't need instructions. The moment you don't make it very clear or start combining stuff or put More interactions beyond one simple gesture then you need to start expanding yourself – provide instructions Because there are too many unknowns

<scribe> ACTION: Jake to write up this point including suggested basic gesture and basic keys lists and add to the bottom of the custom interactions SC document for discussion next time.

<trackbot> Created ACTION-79 - Write up this point including suggested basic gesture and basic keys lists and add to the bottom of the custom interactions sc document for discussion next time. [on Jake Abma - due 2019-11-14].

It would also be good to find examples where feedback works well to make that point easy to picture

Summary of Action Items
[NEW] ACTION: Jake to write up this point including suggested basic gesture and basic keys lists and add to the bottom of the custom interactions SC document for discussion next time.

Summary of Resolutions
[End of minutes]
________________________________
Minutes manually created (not a transcript), formatted by David Booth's scribe.perl<http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> version 1.154 (CVS log<http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2019/11/07 17:27:28 $


--
___________________________________________________

Kimberly Patch
(617) 325-3966
kim@scriven.com<mailto:kim@scriven.com>

www.redstartsystems.com<http://www.redstartsystems.com>
- making speech fly

PatchonTech.com<http://www.linkedin.com/in/kimpatch>
@PatchonTech
www.linkedin.com/in/kimpatch<http://www.linkedin.com/in/kimpatch>
___________________________________________________

-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------