MATF Minutes February 13, 2020

*MATF Minutes February 13, 2020

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


  Mobile Accessibility Task Force Teleconference


    13 Feb 2020


    Attendees

Present
    Kathy, kim_patch, MarcJohlic, Detlev
Regrets

Chair
    Kathleen_Wahlbin
Scribe
    kim_patch


    Contents

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


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

<Kathy> 
https://docs.google.com/document/d/1sszSUKB8t3VuRzxHtOjLfQZjNYCw-xr_EbuMwW7WiGc/edit

Kathy: finalizing language for touch target spacing – working group came 
up with suggested language, which I think is probably fine.
... the only thing I think we've lost or that needs to be clarified is 
touch target size needs to be 52

Detlev: I thought dropping the 52 target for less than 44 – That was my 
understanding I don't know who has worked on this last

Kathy: there was a new proposal as of Tuesday's meeting

Detlev: on Tuesday some criticism of the strains jump from 44 you would 
need any kind of between adjacent targets if 44 bigger and then as soon 
as they get slightly smaller you need 52, which would wreck havoc for 
toolbars.
... people didn't understand why you would seem to increase the 
requirement – I think that's a fair criticism.
... I think it would be okay to have something that's either 44 or if 
the target itself is smaller if you take the target and padding around 
it would be 44 – I think that would sit more easily with the target size 
requirement
... I think that one of the concerns was that people End up making 
target size small, but I don't think that would happen if you require 
clearing 44 x 44. Would people really make pinhead size targets sitting 
a large sea of padding around it? I doubt it.
... but we want to address is pin head size icons and put them close 
together

Kathy: agree

Detlev: 30 x 30 is a common size, that will address this
... maybe need something in normative text, exception or some kind of 
wording where you say you can have smaller targets if there is a 
mechanism to switch to the larger targets – that could be a way of 
getting this past the pushback that we are probably going to face

Kathy: there needs to be away – just as you can meet high contrast – 
that's a technique that's there we could actually have that is a technique

Detlev: settings menu item – would it be the default has to be that big 
or immediately accessible somewhere on the interface without having to 
drill down into some menus or settings – what do you think is realistic?

Kathy: I think he can be the same as what we put as requirements for 
color contrast – just a link in the footer that lets you change the user 
preferences. You could do something similar to that. Available to toggle 
to larger targets.

Detlev: presumably a permanent setting so repeat visitor would find the 
interface already adapted link to the your login or whatever

Kathy: I added that as a technique, we can also integrate that into the 
understanding document

Detlev: does it Need a mention in the normative text – a mechanism for 
switching to larger required touch targets if targets are smaller

Kathy: I would say no because we don't do that for color contrast, it is 
just a technique. Color contrast minimum has the exception for larger 
text, incidental and logotype. That was handled through a technique.

Detlev: we can point to that precedence

Kathy: I would want to handle the same way and say that's the reason – 
that would be my preference rather than trying to make the SC text even 
more complicated

Detlev: this means those who have objections can be shown a way out of 
it if needed
... that was the only suggestion that came out of the meeting

Marc: looking through the Tuesday minutes – suggestion about the side.

Detlev: just a simplification of wording for Furthermost edge

Kathy: top of second page example – important to put something that's 
clarifying what we're talking about. This diagram shows it, we need some 
additional language around it

<MarcJohlic> Mike's suggested wording: "between a control's edge and the 
closest side of any adjacent target..."

Detlev: maybe horizontal toolbar example – that would be a common situation

<scribe> *ACTION:* Detlev to create mockup of horizontal toolbar example

<trackbot> Created ACTION-84 - Create mockup of horizontal toolbar 
example [on Detlev Fischer - due 2020-02-20].

Kathy: Marc if you could weave that language into the understanding, 
that would help people understand
... What's in there as proposed SC is what they came up with after Tuesday

Detlev: it wouldn't be needed for the empty space around the target to 
also respond to the click

Kathy: were not requiring the empty space around – if you have 12 pixels 
we are not saying that 32 of that needs to be active

Detlev: but the plain English summary – overall size of the target must 
be at least 44

Kathy: we need to reword that – increase the space so you have a greater 
likelihood of hitting it

Detlev: worded so the overall space in which the target sits – something 
like that

Kathy: fixing
... I'll add a comment

Detlev: need to make sure there's no misunderstanding that it may only 
apply to one dimension
... size is a bit vague – add something to the horizontal or vertical 
width of the target rather than adding something to the size
... You could place the target in a box size 44 by 44

<Kathy> 
https://docs.google.com/document/d/1sszSUKB8t3VuRzxHtOjLfQZjNYCw-xr_EbuMwW7WiGc/edit#

<scribe> *ACTION:* Kim will send out touch target doc link for last look 
over from group

<trackbot> Created ACTION-85 - Will send out touch target doc link for 
last look over from group [on Kimberly Patch - due 2020-02-20].


    Summary of Action Items

*[NEW]* *ACTION:* Detlev to create mockup of horizontal toolbar example
*[NEW]* *ACTION:* Kim will send out touch target doc link for last look 
over from group


    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/02/13 17:02:09 $


*
*___________________________________________________________

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