14:43:09 RRSAgent has joined #mobile-a11y 14:43:09 logging to http://www.w3.org/2015/04/02-mobile-a11y-irc 14:43:11 RRSAgent, make logs public 14:43:11 Zakim has joined #mobile-a11y 14:43:13 Zakim, this will be WAI_MATF 14:43:13 ok, trackbot; I see WAI_MATF()11:00AM scheduled to start in 17 minutes 14:43:14 Meeting: Mobile Accessibility Task Force Teleconference 14:43:14 Date: 02 April 2015 14:43:16 zakim, this will be 6283 14:43:16 ok, Kathy; I see WAI_MATF()11:00AM scheduled to start in 17 minutes 14:43:35 rrsagent, make log world 14:43:42 meeting: Mobile A11Y TF 14:43:49 chair: Kathy 14:44:57 agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2015Mar/0029.html 14:55:44 WAI_MATF()11:00AM has now started 14:55:51 +Kathy_Wahlbin 14:56:16 agenda+ New time for meeting 14:56:27 agenda+ Survey 14:56:49 agenda+ Comments on note http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Comments_on_Mobile_Accessibility_Note_20150226 14:57:05 agenda+ Responding to comments on Github 14:57:12 agenda? 14:59:20 +Detlev 15:00:26 marcjohlic has joined #mobile-a11y 15:00:30 +Alan_Smith 15:00:54 +Marc_Johlic 15:01:02 Alan_Smith has joined #mobile-a11y 15:01:09 HennyS has joined #mobile-a11y 15:01:50 -Detlev 15:02:36 Mike_Pluke has joined #mobile-a11y 15:02:48 +??P18 15:02:49 +Jeanne 15:02:52 jeanne has joined #mobile-a11y 15:03:16 Jan has joined #mobile-a11y 15:03:18 zakim, who is on the phone? 15:03:18 On the phone I see Kathy_Wahlbin, Alan_Smith, Marc_Johlic, ??P18, Jeanne 15:03:23 zakim, code? 15:03:23 the conference code is 6283 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Jan 15:03:37 zakim, P18 is Mike_Pluke 15:03:37 sorry, jeanne, I do not recognize a party named 'P18' 15:03:51 I put in 6283 as pass code but Zakim tells mie it is not valid... 15:03:58 +[IPcaller] 15:04:04 zakim, ??P18 is Mike_Pluke 15:04:04 +Mike_Pluke; got it 15:04:08 scribe:alan 15:04:09 zakim, [IPcaller] is really Jan 15:04:09 +Jan; got it 15:04:21 takeup next 15:04:38 I'm unable to access the conference bridge. I just get static feedback. 15:04:39 zakim, next item 15:04:39 agendum 1. "New time for meeting" taken up [from Kathy] 15:04:47 +Detlev 15:05:07 worked now 15:05:41 one item on on the agenda is first item is taking about new time for this meeting. 15:05:45 Zakim, mute me 15:05:45 Detlev should now be muted 15:05:55 many interested in joining but in asia but this time is difficult 15:06:17 can we have it earlier in the day or other creative solutions? 15:06:38 +[IPcaller] 15:06:39 Jeanne, anyone on west cost? 15:06:43 JR: I can do do as early as 9am ET 15:06:44 What would be the new time suggestion? 15:06:48 Kathy, yes one person. 15:07:00 + Alan for earlier 15:07:16 +AWK 15:07:36 Mike Shivanik is on west coast 15:08:02 AWK_ has joined #mobile-a11y 15:08:09 can we do survey? 15:08:55 David McDonald has conflict with this exact time. Only can join every other week. 15:09:15 Mark, 9-2 on thursdays is okay 15:10:08 I think Jan said okay with Thursday mornings 15:11:54 should we have a scribe? 15:12:04 Kathy suggested two diff times for meetings for techniques. Review meetings at specific times. 15:12:34 Ah - overlooked that, sorry. 15:12:35 Review meetings to two different times? 15:12:43 + +1.408.425.aaaa 15:13:15 shebanek has joined #mobile-a11y 15:13:29 Asian request for Beijing 15:13:52 currently 11:13 pm for them. 15:14:10 q+ 15:14:32 Mike Shebanek is on west coast usa 15:14:37 q- 15:15:24 Difficult challenge for this with people in different countries. Starts to get to be where time of day is barrier. 15:16:27 Call for concensus on list and not on calls. 15:16:45 Who is speaking? sorry 15:17:02 Andrew, thanks 15:17:22 Trying to be more asinchroneous. 15:17:48 Consensus in list rather than in meetings. 15:17:51 Yes, I know. 15:18:37 ack me 15:18:47 Jan, hard when you have some that go to one meeting and some to another. 15:19:07 There is a lot of value in being able to thrash topics out on the phone, but the CFC process on the list is more inclusive 15:19:11 Move to making sure we do concensous through the list via survey or others. 15:19:28 https://www.w3.org/2002/09/wbs/66524/20150330_survey/results 15:19:30 jakim: next item 15:19:50 zakim, next item 15:19:50 agendum 2. "Survey" taken up [from Kathy] 15:20:24 Started on operable. 15:20:54 TOPCI: 1. 3.1 Keyboard Control for Touchscreen Devices 15:20:54 discuss different one, any missing, have people walk through their suggestions. 15:21:30 3.1 Keyboard control for touchscreen devices 15:21:45 Reviewing each response. 15:22:09 don't need to be in WCAG but anything new as well. 15:22:20 Touch and mouse control also important 15:22:49 q+ 15:23:20 Mouse could be other device as well. 15:23:45 Detlev, perhaps pointer control. 15:23:51 for example mouse 15:24:22 Kathy also taking notes of comments. 15:24:50 for touch devices in brackets (using touch and keyboard) 15:25:16 David made comment on not seing keyboard trap and do we need discussion of drag and drop. 15:25:35 I agree that we need keyboard trap 15:25:40 Kathy did see trap recently, so it is important 15:26:05 detlev; are we also talking about keyboard and screen readers and swipe? 15:26:15 I also agree that we need to address keyboard trap (or trap in general) 15:26:37 Kathy, touch and pointer control also not being trapped for touch. 15:27:06 Is opporability is better wording? 15:27:28 Ensuring touch access control for all functionality' sounds more like it should be associated to 3.3 Touchscreen Gestures as 3.1 focuses on keyboard operability. 15:28:03 "Defining the hover, focus, selected and touch (regular, long) states": these states mostly have a platform-specific implementation so what should the content author define here apart from adequate visible focus (SC 2.4.7)? This might be rendered as "Use focus, hover and select states consistently and in a way that follows the respective platform conventions", or similar. 15:28:47 Kathy, only thing worried about neet to have focus state that is visible. 15:29:20 May need to clarify further, have behaviors of all the ways we interact. 15:29:36 hover, and other have the affordance that something is there. 15:29:44 Mike: trap issue. 15:29:55 where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus 15:30:57 Mike could not get his results entered. 15:31:13 Kathy saw this this morning, not sure what is going on with survey. 15:31:53 His comments are in there, no worries. 15:32:20 Kathy when we are looking at keyboard or touch. Kim would share on voice control if on call. More for UAG site. 15:32:40 Anything we should say or include for other ways people are interacting? 15:33:04 Andrew: how to plan for a good voice interaction model. 15:33:28 sumarizing for action. 15:33:46 Sorry, that was Mike 15:34:04 Kathy would we group voice with touch ? 15:34:14 Or specific techniques for switch. 15:34:21 Jan, can emulate both. 15:34:39 Jeanne, likes idea of addressing switch directly. 15:34:49 Give the appearance of not addressing it otherwise. 15:35:00 Have section for "other" 15:35:18 Kathy, what if touch, point and other input devices 15:35:43 Jan, not quite sure about this. 15:36:16 What is keyboard is sequential, touch is ability for random access. Voice is another random access method 15:36:28 Into the ui even with out actual button there. 15:37:06 Alan, keyboard can also do next paragraph, sentence, etc. 15:37:26 Jan, this is an access issue 15:37:46 Mode, is a radial thing. 15:38:16 Voice we can do voice sequeential and randomly. 15:38:34 Kathy put this into three groups in document. 15:38:52 any techniques for random and seq. 15:39:12 Not putting notes on wiki put on seperate word doc. 15:39:36 Detlev, may get things not focusable. 15:39:51 Kathy what about grouping, and how people actually access it. 15:40:20 Jan, still seq. but hierarcial. Are you asking about random? 15:40:38 Kathy, any technique in voice or switch we need to have in here? 15:41:09 Jan, when a switch emulates a mouse, button size is still important. 15:42:01 May not be something to address here. Will think about this more. will look at a whole later. 15:42:12 TOPIC: Touch Target Size and Spacing 15:42:22 next item is 2.3.2 15:42:39 Providing adequate touch target size / Ensuring that touch targets are large enough to touch accurately without magnification Provide adequate spacing between touch targets 15:42:57 Jan talking about his comment: Another maybe advisory thing is to provide a viewer showing what's under the finger in apps taking path input (maybe that's for the touch/mouse section) 15:43:07 Many apps these days you want to do fine work. 15:43:26 One technique is a viewer under your finger. 15:43:48 Kathy to go under touch and pointer control. 15:44:00 Kathy, goes with Mikes point on affordance. 15:46:11 -Jeanne 15:46:31 -Marc_Johlic 15:46:37 Alans comment on zoom maginication when touching close to a link button. 15:46:55 Mikes comment: Touch target is not defined. It is not uncommon to use software to disambiguate the intended touch target. In such a case the concept of spacing between touch targets is difficult to define. Also, the visible target can be quite small (e.g. a down arrow) as long as it is sufficiently far away from other active controls. 15:47:14 really talking about area inwhich the actual area where you touch the control. 15:47:46 What are talking about with touch target. area in which you touch it it activates a specific control. 15:47:57 Detlev, area that activates the target, 15:48:21 Much larger area that actually activates the target. Or little area you see. 15:48:57 Jan, agrees. To him, the surrounding area is still the touch target. 15:49:12 +Jeanne 15:49:16 Provide adequate spacing, the space in between is inactive. 15:49:37 When targest are small inactive area is more important. 15:49:58 Need to be careful of sugesting spacing. 15:50:54 More concerned that when you touch an element you don't activate the wrong one you did not want to touch. 15:51:33 Provide adequate spacing between elements. Have two items on this. 15:51:39 Zakim, mute me 15:51:39 Detlev should now be muted 15:51:54 Mike, avoided putting size and spacing in european guidelines. 15:52:14 There are minimum sizes defined in dev docs for ios and android. 15:52:26 UAAG says they have to follow dev docs. 15:52:33 Mike is okay with have both. 15:53:05 ack me 15:53:32 detlev: on his comments for touch: better to say imput mode independent. 15:53:44 UAAG SC on following dev docs -> http://w3c.github.io/UAAG/UAAG20/#sc_512 15:54:07 One technique avoid techniques when screen reader is turned on some dont work. 15:54:17 Provide fall back to drag and drop 15:54:37 fall back for delete icon via drag and drop to trash can. 15:54:38 -[IPcaller] 15:55:18 Alan, is that same as keyboard equiv for all touch 15:55:49 detlev; may have long press and delete key may not be mutually exclusive. 15:55:55 kathy, any more. 15:56:09 Device gesture 3.3.3 15:57:06 Jan, wording needs to be explained, using device buttons are rair on things. 15:57:36 actually going over 4. 3.4 Device Manipulation Gestures 15:57:53 David: might need to rename the second technique to make it clearer... I'm bouncing between arrow on a keyboard and home button on device in my mind. 15:58:01 Are these hard or soft buttons? 15:58:25 Things like android back button. 15:58:33 Is this software or hard key? 15:58:42 Jan, considers this a hardware key. 15:59:07 new android 5 active actually has hardware keys for these that are soft on other devices. 15:59:28 Some use this for other functions, and actions are not consistance. 15:59:39 Jan, same within device useage. 15:59:48 any last comments?: 15:59:59 Kathy will put wiki page together for these notes. 16:00:19 Will create survey for next week for list of techniques. 16:00:29 Kathy thanks and bye. 16:00:29 -Jan 16:00:30 -Detlev 16:00:31 - +1.408.425.aaaa 16:00:31 -Jeanne 16:00:52 zakim, list attendees 16:00:52 As of this point the attendees have been Kathy_Wahlbin, Detlev, Alan_Smith, Marc_Johlic, Jeanne, Mike_Pluke, Jan, [IPcaller], AWK, +1.408.425.aaaa 16:01:01 rrsagent, make minutes 16:01:01 I have made the request to generate http://www.w3.org/2015/04/02-mobile-a11y-minutes.html Kathy 16:01:08 rssagent make minutes 16:01:15 rrsagent, make logs public 16:01:24 -Mike_Pluke 16:01:55 regrets+ Kim 16:02:51 regrets+ David 16:02:56 rrsagent, make minutes 16:02:56 I have made the request to generate http://www.w3.org/2015/04/02-mobile-a11y-minutes.html Kathy 16:02:59 rrsagent, make logs public 16:03:09 rssagent, make minutes 16:03:32 regrets + David 16:03:39 regrets +Kim 16:03:43 rrsagent, make minutes 16:03:43 I have made the request to generate http://www.w3.org/2015/04/02-mobile-a11y-minutes.html Kathy 16:03:45 rrsagent, make logs public 16:04:12 zakim, aaaa is Mike 16:04:12 sorry, Kathy, I do not recognize a party named 'aaaa' 16:04:22 zakim, aaaa is sherbanek 16:04:22 sorry, Kathy, I do not recognize a party named 'aaaa' 16:04:29 zakim, aaaa is shebanek 16:04:29 sorry, Kathy, I do not recognize a party named 'aaaa' 16:07:04 -Kathy_Wahlbin 16:07:06 -Alan_Smith 16:12:06 disconnecting the lone participant, AWK, in WAI_MATF()11:00AM 16:12:07 WAI_MATF()11:00AM has ended 16:12:07 Attendees were Kathy_Wahlbin, Detlev, Alan_Smith, Marc_Johlic, Jeanne, Mike_Pluke, Jan, [IPcaller], AWK, +1.408.425.aaaa 17:06:21 jeanne has left #mobile-a11y