- From: Kim Patch <kim@redstartsystems.com>
- Date: Thu, 18 Aug 2016 12:19:05 -0400
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <57B5DFF9.70701@redstartsystems.com>
*MATF Minutes 18 August 2016 link:
https://www.w3.org/2016/08/18-mobile-a11y-minutes.html*
*
Text of minutes:*
Mobile Accessibility Task Force Teleconference
18 Aug 2016
See also: IRC log <http://www.w3.org/2016/08/18-mobile-a11y-irc>
Attendees
Present
Kathy, jeanne, marcjohlic, DavidMacDonald, Kim, Alan
Regrets
Chair
Kathleen_Wahlbin
Scribe
Laura, Kim
Contents
* Topics <https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#agenda>
1. SC Pointer with Assistive Technology -
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#SC_Shortname
<https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#item01>
2. Accidental Activation -
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3
<https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#item02>
* Summary of Action Items
<https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#ActionSummary>
* Summary of Resolutions
<https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#ResolutionSummary>
------------------------------------------------------------------------
<Kathy>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#SC_Shortname
SC Pointer with Assistive Technology -
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#SC_Shortname
<Kim> David: changed to pointer rather than touch. Do have concerns
about this -- think will be constantly explaining that pointer does
include touch
<Kim> Kathy: Patrick did say that for some of them we might want to say
touch. The specific type of pointer in this case is touch. So it might
be okay to talk about touch rather than pointer here.
<Kim> David: I'm fine with that
<Kim> Kathy: if any of the assistive technology starts remapping touch
gestures it applies
<Kim> David: platform assistive technology specifically -- the stable
stuff that's shipping with the OS
<Kim> David: when we do get into Windows and tablets world, though we
people saying this should work with draws to, but that's not what we're
requiring for this. It has to work with AT but not touch
<Kim> David: that's just warning about a discussion coming up
<Kim> General agreement that touches better than pointer for this one
<Kim> Marc: is talkback a good example here - does it come on the
device? is narrator better example?
<Kim> David: it does ship with it
<Kim> Chris: base android devices all come with it
<Kim> Kathy: and then we have the Amazon screen reader -- that's similar.
<Kim> David: broad and edits from Patrick. Just the top level where I
didn't have pointer.
<Kim> Kathy: keep it with touch right now -- we are talking about a
specific type of pointer. Pointer is more global
<Alan_Smith> Alan is good with Level A for touch
<Kim> Kathy: priority level comments?
<jeanne> +1
<Alan_Smith> Can you put the link back in irc? when irc loads it removes
all rows of text/converstations prior to me joining
<davidmacdonald>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#Benefits
<chriscm> SOrry, another meeting got to go! Didn't want to interupt.
<Kim> Alan: includes switch activated?
<Kim> David: I've never heard of problems because it's so granular and
you're going from item to item. I'll put it in the boneyard is a possibility
<Kim> Alan: I'll try it on iOS to see
<Kim> Kathy: in the benefits, need documentation to prove that this is
an issue -- pretty cut and dried that this is a problem, but are there
any links to research or other things to prove that this is indeed a
user issue.
<Kim> Discussion about types of resources -- sometimes it's people in
the group seeing this happen with users. User groups...
<Kathy> http://www.applevis.com/search/site/gestures%20with%20voiceover
<Kim> Kathy: link: all of the queries about gesture with voiceover. I
think we can link to this
<Alan_Smith> I checked Switch control on iPad and tap is supported as a
switch but it is not dependent upon target size. It does support long
tap though.
<marcjohlic> +1
<marcjohlic> +1 on Touch w/ AT being ready
<Kim> David: this ready to go?
<Kathy>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3#Description_.28Intent.29
*RESOLUTION:
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#Benefits
ready for WCAG*
<davidmacdonald> https://github.com/w3c/wcag21/issues/3
<davidmacdonald> https://github.com/w3c/wcag21/issues/2
<davidmacdonald> These are examples of submitted SC as requested by
Andrew with template here https://github.com/w3c/wcag21/issues/1
<Kim> Alan: low vision user needing to use speech -- is that speech
input? Do we make it clear that assistive technology is voiceover?
should we have that in the very beginning -- it's not till you read
through it that you realize that assistive technologies is voiceover and
talk
<Kim> Kathy: can be anything
<Kim> Kathy: if any AT remaps it would fall under this
<Kim> David: written for specific use case but the description allows us
to widen it
Accidental Activation -
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3
<Kim> Kathy: we have this almost completed
<Kathy>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Target_Size
<Kim> Kathy: we will pick this up next week. A couple things to think
about we need some evidence for this to insert. Touch target size Mark
wrote up, I made edits. I started looking back at research. Couple
things stood out. Android, Apple use CSS pixels. I put a summary of
research and touch target sizes people were recommending with minimum.
Right now we are recommending smaller than what the...
<Kim> ...research is showing. Need to discuss that next week. In
boneyard there's a link to the summary of research -- Patrick had actual
millimeter size based on devices. I want to challenge the size that
we've got. Take a look. I made it easy to digest the research --
summaries are in there under evidence. Look at what I put and think
about it. We will have to make a decision next week.
<Kim> Mark: easier to check pixels rather than measure millimeters, but
it seems like millimeter measurement would be easier to follow across
devices
<Kim> Kathy: if you look at Patrick research if you set a pixel size
you've got different millimeters for different things
<Kim> Marc: if there's a way to make millimeters rather than pixels --
<Kim> Kathy: but you can't test that way
<Kim> Kathy: Apple went from pixels the point after the retina display
came out. That's when they changed their recommendations from pixels the
points. We need to look at this closely.
<Kim> David: I think the 44 and 20 were placeholders
<jeanne>
https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Summary_of_Research_on_Touch/Pointer_Target_Size
<Kim> Kathy: it was -- we have to finalize this. Look at Fitt law. Lots
of links all on page.
<Kim> scribe: Kim
Summary of Action Items
Summary of Resolutions
1. https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Pointer_with_Assistive_Technology#Benefits
ready for WCAG
<https://www.w3.org/2016/08/18-mobile-a11y-minutes.html#resolution01>
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.144 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2016/08/18 16:15:05 $
--
___________________________________________________
Kimberly Patch
President
Redstart Systems
(617) 325-3966
kim@redstartsystems.com <mailto:kim@redstartsystems.com>
www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly
Blog: Patch on Speech
+Kim Patch
@RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________
Received on Thursday, 18 August 2016 16:19:37 UTC