MATF Minutes January 30, 2020

*MATF Minutes January 30, 2020

Link: *https://www.w3.org/2020/01/30-mobile-a11y-minutes.html*
*
*Text:*

Mobile Accessibility Task Force Teleconference


    30 Jan 2020


    Attendees

Present
    Kim_Patch, JakeAbma, Kathy, Jennifer, Marc
Regrets

Chair
    Kathleen_Wahlbin
Scribe
    Kim_Patch


    Contents

  * Topics <https://www.w3.org/2020/01/30-mobile-a11y-minutes.html#agenda>
     1. multi-input discussion
        <https://www.w3.org/2020/01/30-mobile-a11y-minutes.html#item01>
     2. target size
        <https://www.w3.org/2020/01/30-mobile-a11y-minutes.html#item02>
  * Summary of Action Items
    <https://www.w3.org/2020/01/30-mobile-a11y-minutes.html#ActionSummary>
  * Summary of Resolutions
    <https://www.w3.org/2020/01/30-mobile-a11y-minutes.html#ResolutionSummary>


------------------------------------------------------------------------


      multi-input discussion

https://docs.google.com/document/d/13QWLthBoEU6xuJQ4UrYOwuvJp0a42Z70JRjAsjtv1m4/edit#heading=h.69rdheamia4t

<MarcJohlic> 
https://docs.google.com/document/d/1prtMUWGIjerl4pVXLxknP9NId2Z2qIsUzFYOeVmftPU/edit#

Discussion in document – user challenges

Kathy: type of element doesn't match what the interaction should be – 
aria, if you don't follow the aria practices guide – practices to use 
arrow key a lot of developers will use pad. You can press the arrow keys 
but you need to use the tab – just an example to see where we see issues 
not necessarily just WCAG failures
... keyboard interaction doesn't match what the role is – best practice, 
but not failure currently

<Jennifer> be right back

Kathy: looking at challenges surrounding mobile and different types of 
interactions – thinking about multi-input, there still seem to be 
challenges with end-users a lot within native apps and a lot within 
other types of things. A lot of times this is for designers and figuring 
out what the interaction is going to be. So part of the multi-input 
discussion exercise is just to understand could we write a document for 
people who are designing.
... just as the cognitive task force is creating a lot of best practices 
for users, one of the challenges that Kim brought up was the whole 
multi-input and that people aren't thinking of the challenges within 
having multi-input. Starting the conversation about user challenges was 
for me trying to figure out what are we talking about here, and is this 
something that we should think about writing about, and if so what would 
that contain.
... and also if there are gaps under which can and things that can be 
filled by a user challenge that we might suggested new success criteria
... this is an exercise to start thinking about all the things that 
could be a challenge within multi-input or multiplatform use

Jake: this will just be an ongoing process – so it will be good to pay 
more attention to possible issues in the coming months to see what we 
can have?

Kathy: yes.
... I think this is good exercise – keep in mind how people are using 
different inputs, different platforms and multi-input combinations
... if you think of other items add to this list, and we'll see where we 
take it from this point

<MarcJohlic> DM update to Spacing Between Touch Targets 
https://docs.google.com/document/d/1ejG_7yaCI2xbEPqFZCbJgqGuu_kplEMtsO-XYJVbTkg/edit


      target size

<JakeAbma> 
https://lists.w3.org/Archives/Public/w3c-wai-gl/2020JanMar/0121.html

Jake: rewrite talking about 52

Kathy: we said if 44 it didn't need spacing - he's requiring 52 for 
everything
... we should talk through this next week

rsagent, make minutes


    Summary of Action Items


    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: 2020/01/30 17:13:37 $

** *
*___________________________________________________________

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>
___________________________________________________