- From: Kim Patch <kim@redstartsystems.com>
- Date: Thu, 29 Oct 2020 11:55:10 -0400
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, "ran@w3.org" <ran@w3.org>
- Message-ID: <892106c7-0f65-c334-318d-60af99775cc7@redstartsystems.com>
*MATF Minutes October 29, 2020
*
*Link: https://www.w3.org/2020/10/29-mobile-a11y-minutes.html*
*
Full text of minutes:*
Mobile Accessibility Task Force Teleconference
29 Oct 2020
Attendees
Present
JakeAbma, Kim, Sukriti
Regrets
Chair
Kimberly_Patch
Scribe
Kim_patch
Contents
* Topics <https://www.w3.org/2020/10/29-mobile-a11y-minutes.html#agenda>
* Summary of Action Items
<https://www.w3.org/2020/10/29-mobile-a11y-minutes.html#ActionSummary>
* Summary of Resolutions
<https://www.w3.org/2020/10/29-mobile-a11y-minutes.html#ResolutionSummary>
------------------------------------------------------------------------
https://github.com/w3c/wcag/issues/1432
https://docs.google.com/document/d/1_EHFVE-p4jEtKFa2jMEUruSvu6iv-Vt7UxRW9SrHTCQ/edit#heading=h.tuvbez1itgj0
Jake: current wording doesn't prevent overlapping targets and
overlapping targets would make target size smaller
... this is not the original intent – if the target spacing is
overlapping it's 18, not 24
... because it says the target and the nearest edge of the closest
target. You can end up with targets of 8 x 8 pixels and you need to add
it on top because four plus eight is 12, but then they are only 16 pixels.
Sukriti: but if we don't allow spacing to be part of this we
dincentivize that behavior. I really think we should go with a 24 pixel
version of the AAA version
Jake: the issue is that breaks a lot of webpages.
Sukriti: the other counterargument that people were making is 24 is not
enough. We could say to keep it online that spacing cannot overlap. It
becomes a tough thing to explain within an already complex – center of
the target.
Jake: the disadvantage of the 24 pixel will be all these links need to
have a lot more padding four links that aren't part of a sentence or
block of text
... the other option, they don't need padding the only thing that they
need is to have a margin top of eight pixels. You leave those targets
alone, but you need to create way more margin. In the other case you
need to create bigger target areas. The result is the same but the way
to adjust everything is completely different.
... although we would like the 24 the other one might work better
because it doesn't require as much to be adjusted
... target 18 high you do not have to do anything about it in the second
version, but if there is no other target around you do not need to
change it in the second version
Sukriti: if -looking is not an issue just hitting a target, that makes sense
... how can we explain this well
Added overlapping to address this issue
https://docs.google.com/document/d/1_EHFVE-p4jEtKFa2jMEUruSvu6iv-Vt7UxRW9SrHTCQ/edit#heading=h.tuvbez1itgj0
<scribe> *ACTION:* Sukriti will send note to Alastair about the change
<trackbot> Error creating an *ACTION:* could not connect to Tracker.
Please mail <sysreq@w3.org> with details about what happened.
<scribe> *ACTION:* Sukriti will send note to Alastair about the change
<trackbot> Error creating an *ACTION:* could not connect to Tracker.
Please mail <sysreq@w3.org> with details about what happened.
Summary of Action Items
*[NEW]* *ACTION:* Sukriti will send note to Alastair about the change
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
(CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2020/10/29 15:53:21 $
**___________________________________________________________
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>
___________________________________________________
Received on Thursday, 29 October 2020 15:55:35 UTC