15:04:03 RRSAgent has joined #mobile-a11y 15:04:03 logging to http://www.w3.org/2015/03/12-mobile-a11y-irc 15:04:05 RRSAgent, make logs public 15:04:05 Zakim has joined #mobile-a11y 15:04:07 Zakim, this will be WAI_MATF 15:04:07 ok, trackbot, I see WAI_MATF()11:00AM already started 15:04:08 Meeting: Mobile Accessibility Task Force Teleconference 15:04:08 Date: 12 March 2015 15:04:19 agenda+ WAI charters 15:04:24 zakim, who's here? 15:04:24 On the phone I see Jeanne, TomB, Alan_Smith, [IPcaller], ??P18, David_MacDonald, Marc_Johlic 15:04:26 On IRC I see RRSAgent, marcjohlic, jon_avila, Alan_Smith, Jan, AWK, Mike_Pluke, jeanne, slee, Joshue, MichaelC, trackbot 15:04:40 + +1.703.637.aaaa 15:04:41 zakim, [IPcaller] is probably Jan 15:04:42 +Jan?; got it 15:04:42 agenda+ Comments on note (changes will be included in a future version of the note) 15:04:52 zakim, I am aaaa 15:04:53 +jon_avila; got it 15:05:04 agenda+ Next Steps – Next meeting Thursday, March 19 15:05:09 zakim, who is on the phone? 15:05:10 On the phone I see Jeanne, TomB, Alan_Smith, Jan?, ??P18, David_MacDonald, Marc_Johlic, jon_avila 15:05:42 zakim, ??P18 is MikeB 15:05:42 +MikeB; got it 15:06:45 scribe: jon_avila 15:06:51 zakim, take up item 1 15:06:51 agendum 1. "WAI charters" taken up [from jeanne] 15:07:43 David has joined #mobile-a11y 15:07:55 jeanne: WAI charter -- has to reapproved every 3 years. We need a certain percentage of membership to respond. 15:08:24 https://www.w3.org/2002/09/wbs/33280/wai_2015/results 15:08:29 shebanek has joined #mobile-a11y 15:08:38 jeanne: check with AC reps to respond for charters 15:09:06 jeanne: all WAI charters are up. 15:09:36 + +1.408.425.aabb 15:10:25 Jeanne: can look up AC rep if you don't know who it is. 15:10:33 -Alan_Smith 15:10:42 zakim, aabb is MikeS 15:10:42 +MikeS; got it 15:11:29 +Alan_Smith 15:13:13 jeanne: we have 4 so far and it's been out for two weeks. 15:14:30 jeanne: Helps to show membership that we care about accessibility and we want the work to go forward. A lot of responses would be helpful. 15:14:59 topic: CSUN debrief 15:15:12 jeanne: CSUN debrief from those who were at CSUN. 15:15:38 Look up AC reps here: https://www.w3.org/Member/ACList.php 15:15:58 jeanne: Kathy and I presented on Friday @ 8am -- had a lot of questions. Lot of people wanted to get involved. People were excited to see the note. 15:16:38 jeanne: attended another session where presenter said WCAG had nothing to do with mobile 15:18:20 Jon: I had a mobile presentation on ARIA, but I couldn't be there. 15:18:31 Jon: Only one person there as it wasn't advertised well 15:19:00 Jon: Tests of 30 different ARIA roles in various mobile browsers 15:19:11 Jon: Some controls like spin buttons not seen at all 15:19:27 Jon: Some controls with keyboard equivs performed very poorly 15:19:42 Jon: I will paste in a link 15:20:01 Jon: Or you can contact me directly 15:20:19 MikeS: That was a great session, really well done...ability to compare browsers 15:20:44 Link to download my presentation on ARIA and mobile http://info.ssbbartgroup.com/csun2015/ 15:20:57 MikeP: Back to comment on WCAG not applying to mobile 15:21:29 MikeP: Leading work on EU public procurement standard -- developed requirements related to mobile. 15:21:36 Kim has joined #mobile-a11y 15:22:05 There is one particularly outspoken individual who evangelizes the "WCAG doesn't work for mobile" view. 15:22:14 MikeP: US Access Board wanted to use WCAG for mobile. At first we weren't going that direction but then we started to look at it and then took a strong view and found that there was a lot of commonalities 15:22:24 +Kim_Patch 15:22:45 Think that we just need to say it does more and keep producing evidence to support the point 15:22:51 rrsagent, make minutes 15:22:51 I have made the request to generate http://www.w3.org/2015/03/12-mobile-a11y-minutes.html jeanne 15:24:07 david: First time on mobile TF -- as we go further we need to get more granular on advice, 15:25:14 MS: Launched Android app and presented on what is Yahoo is doing on iOS and Android. 15:25:28 Aviate - A launcher app from Yahoo that is accessible 15:25:53 Aviate only available for Android 15:26:36 jeanne: WAI 2020 meetings were also at CSUN but not well advertised -- talked about future direction of WCAG. Talked about what the mobile TF had done. 15:27:06 jeanne: could do separate normative requirements and not change WCAG. 15:27:35 jeanne: our model was to get a group of people working in a narrow area. We could start to make normative requirements in this area. 15:27:59 jeanne: still in early stages of this. We aren't saying yes yet. 15:32:22 MS: maybe we are looking at this backwards. We are providing a really smart and proper system and the justice system to come to a conclusion that they do need this work -- because they will indeed need this work because they could be sued over something they weren't aware of. We shouldn't be afraid of the work we are doing and we should push forward. 15:33:06 Alan: Even DOJ and ADA refer to WCAG even if they don't have it as a binding requirement. 15:34:06 jeanne: in the US there is not specified website accessibility standards for non-government or education sites. Lawsuits have been settled with WCAG. 15:35:39 Jon: I've looked at some of settlements, they are referring WCAG for mobile and I've seen them reference ATAG and WCAG 15:36:12 Jon: But sometimes its stated generally which can cause some uncertainty 15:36:57 MS: Accessibility will be built into Apple Watch -- do we need to update notes? 15:37:15 jan: Think it is contemplated sufficiently 15:37:43 zakim, take up next 15:37:46 agendum 2. "Comments on note (changes will be included in a future version of the note)" taken up [from jeanne] 15:38:23 jeanne: Comments from EO -- we didn't finish from two weeks ago 15:38:40 kim: Jeanne were you also checking github for comments? 15:39:00 jeanne: we did get a number of comments in github which is cool 15:39:18 https://github.com/w3c/Mobile-A11y-TF-Note/issues 15:40:21 jeanne: Wanted to mention mobile web checker. Had a good conversation with colleague who is making a mobile checker that hopefully will be in public beta. 15:41:09 jeanne: Will help people who are creating sites or app for the desktop but need to know how it will work on mobile. 15:41:37 jeanne: Eager to get accessibility testing into checker. Gave him example of touch size -- interested in getting that into checker. 15:41:59 jeanne: invites people to contribute accessibility tests into github. 15:42:53 jeanne: drop jeanne an email if you need more information 15:43:32 jeanne: not testing for conformance but helpful app for developers. 15:43:40 jeanne@w3.org is my email 15:43:58 zakim, who is speaking? 15:44:08 jon_avila, listening for 10 seconds I heard sound from the following: Alan_Smith (2%), Kim_Patch (19%) 15:44:45 alan: 9mm number comes from Android developers and other sources 15:45:15 jeanne: 9mm is starting place for conversation -- may not be final number we recommend. 15:46:33 kim: let's go from bottom up on github issues as it's newest. 15:48:01 kim: Commenter: should consider add click as it's not specific to touch interface 15:48:15 jeanne: may be slightly different as click misses the point 15:48:25 jan: A click is a mouse or touch down and then up. 15:50:07 alan: could put in equivalent or device supported equivalent 15:51:34 jeanne: under 3.3 second bullet 15:51:39 jan: click would be fine. 15:51:44 Activating elements via the mouseup or touchend event. Using the mouseup or touchend event to trigger actions helps prevent unintentional actions during touch and mouse interaction. 15:53:37 Activating elements via the click event. Using the mouseup or touchend event to trigger actions helps prevent unintentional actions during touch and mouse interaction. Mouse users clicking on actionable elements (links, buttons, submit inputs) should have the opportunity to move the cursor outside the element to prevent the event from being triggered. This allows users to change their 15:53:37 minds without being forced to commit to an action. In the same way, elements accessed via touch interaction should generally trigger an event (e.g. navigation, submits) only when the touchend event is fired (i.e. when all of the following are true: the user has lifted the finger off the screen, the last position of the finger is inside the actionable element, and the last position of the 15:53:38 finger equals the position at touchstart). 15:54:19 kim: more that it was unclear -- the comment helps to make the connection clear. 15:54:36 rrsagent, make minutes 15:54:36 I have made the request to generate http://www.w3.org/2015/03/12-mobile-a11y-minutes.html jeanne 15:54:47 +1 15:54:55 +1 15:55:00 +1 15:55:03 +1 15:56:17 kim: 3.1 keyboard control. Commenter: VoiceOver and Talkback work different in how they place content without text in reading order when screen reader is active. 15:56:36 kim: Commenter says e.g. spans with no text but background image are not accessible on Anrdoid w/ Talkback 15:57:06 jan: describes problem that keyboard interaction works different on different platforms 15:57:29 Many considerations that are nominally for keyboard (such as focus order, and the fact that elements that are actionable need to also be keyboard-focusable) are equally valid for users of screen readers on touch-screen devices. While VoiceOver/iOS (because of the way its navigation works) lets users focus even on non-focusable elements (such as a for instance), TalkBack/Android does... 15:57:30 ...not, depending on the specific way a control was coded...in most cases, if there's no actual text content (so for instance an empty with only some CSS-based indicator, like an icon font or CSS background image, will simply not be focusable/navigated to, and therefore cannot be triggered). 15:57:32 It may be worth mentioning this aspect as well? 15:57:52 The above is the comment on 3.1 15:58:42 action: jeanne to update the editor draft in 3.3 bullet: change "Activating elements via the mouseup or touchend event." to "Activating elements via the click event". 15:58:42 Created ACTION-23 - Update the editor draft in 3.3 bullet: change "activating elements via the mouseup or touchend event." to "activating elements via the click event". [on Jeanne F Spellman - due 2015-03-19]. 15:59:08 MS: what we need to say is that we need to support keyboard access when screen reader is not running. 16:00:24 Can we get a confirmationon the suggested Android Accessibility helper app is Avaite. I only see Yahoo Aviate Laucher in Google Play 16:01:25 MS: we want people to understand that by supporting keyboard control you are supporting other class of input devices. 16:01:31 +1 16:01:32 alan: +1 16:02:04 kim: Any last things? 16:02:08 -Alan_Smith 16:02:10 -Marc_Johlic 16:02:13 -David_MacDonald 16:02:16 -TomB 16:02:35 action: MikeS to write an proposal on the importance of the keyboard for a range of other devices. 16:02:35 Created ACTION-24 - Write an proposal on the importance of the keyboard for a range of other devices. [on Mike Shebanek - due 2015-03-19]. 16:02:40 zakim, list attendees 16:02:40 As of this point the attendees have been Jeanne, TomB, Alan_Smith, David_MacDonald, Marc_Johlic, +1.703.637.aaaa, Jan?, jon_avila, MikeB, +1.408.425.aabb, MikeS, Kim_Patch 16:03:00 shebanek has left #mobile-a11y 16:03:03 zakim, make minutes 16:03:03 I don't understand 'make minutes', jon_avila 16:03:07 -MikeS 16:03:19 Mike_Pluke has left #mobile-a11y 16:03:22 RRSAgent, make minutes 16:03:22 I have made the request to generate http://www.w3.org/2015/03/12-mobile-a11y-minutes.html jon_avila 16:03:43 RRSAgent, make logs public 16:03:50 zakim, bye 16:03:50 leaving. As of this point the attendees were Jeanne, TomB, Alan_Smith, David_MacDonald, Marc_Johlic, +1.703.637.aaaa, Jan?, jon_avila, MikeB, +1.408.425.aabb, MikeS, Kim_Patch 16:03:50 Zakim has left #mobile-a11y 16:04:04 zakim, who is still on the phone?