15:49:48 RRSAgent has joined #mobile-a11y 15:49:48 logging to http://www.w3.org/2014/12/18-mobile-a11y-irc 15:49:50 RRSAgent, make logs public 15:49:50 Zakim has joined #mobile-a11y 15:49:52 Zakim, this will be WAI_MATF 15:49:52 ok, trackbot; I see WAI_MATF()11:00AM scheduled to start in 11 minutes 15:49:53 Meeting: Mobile Accessibility Task Force Teleconference 15:49:53 Date: 18 December 2014 15:50:12 chair: Kimberly_Patch 15:50:41 agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Dec/0006.html 15:51:09 Agenda+ Q&A Note assignments / status 15:51:11 Agenda+ Platform capabilities finish discussion https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Platform_Capabilities 15:51:12 Agenda+ Comments on note so far https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Note:_WCAG_2.0_and_Mobile 15:51:14 Agenda+ Next steps – next meeting January 8 15:52:12 Regrets + Kathleen_Wahlbin, Alan 15:54:29 jeanne has joined #mobile-a11y 15:59:56 WAI_MATF()11:00AM has now started 16:00:03 +Kim_Patch 16:02:02 +Jeanne 16:02:14 zakim, who is on the phone 16:02:14 I don't understand 'who is on the phone', jeanne 16:02:37 +??P16 16:03:10 MichaelC has changed the topic to: Mobile Accessibility Task Force; Teleconferences Thursdays 11 am Eastern; Zakim +1.617.761.6200 passcode 6283 16:04:07 Jan_ has joined #mobile-a11y 16:04:33 Detlev has joined #mobile-a11y 16:05:28 Brent has joined #mobile-a11y 16:06:05 +[IPcaller] 16:06:16 +Detlev 16:06:22 zakim, [IPcaller] is really Jan 16:06:22 +Jan; got it 16:06:32 jon_avila has joined #mobile-a11y 16:06:50 +jon_avila 16:07:37 + +1.512.276.aaaa 16:08:00 scribe: jon_avila 16:08:59 http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Note:_WCAG_2.0_and_Mobile 16:09:14 jeanne: Section 4: discussion on virtual keyboard to type of data entry required. 16:09:25 zadim, aaaa is really Brent 16:09:46 zakim, aaaa is Brent 16:09:46 +Brent; got it 16:09:47 zakim, aaaa is really Brent 16:09:48 sorry, Brent, I do not recognize a party named 'aaaa' 16:10:07 jeanne: overall very positive things. Issue for people who are using phone with VoiceOver changing keyboard for different fields can be an issue. 16:10:27 KP: D1 on the note 16:10:56 jan: calling different variants of the system keyboard. User need to know how the system works. 16:11:48 jeanne: not so much about numbers and general text but more of an issue for dot and at sign for urls 16:12:07 AWK has joined #mobile-a11y 16:12:10 mc: OS feature and not web app feature 16:12:22 jan: OS features -- perhaps give OS developers advice 16:12:43 jeanne: could this be a UAAG feature to give people an option to standardize keyboard 16:12:57 q+ 16:13:04 q+ 16:13:35 mc: UAAG level thing seems reasonable 16:14:48 mc: spec on input editors API 16:14:53 -> http://www.w3.org/TR/ime-api/ Input Method Editor API 16:15:33 mc: separate concerns about how this reacts 16:16:02 kp: any other questions? 16:16:09 q- 16:17:09 q- 16:17:34 +1 to supporting HTML guidelines 16:20:08 kp: any thoughts on d2? auto form fields 16:20:59 detlev: don't see particular issue accessibility wise 16:21:44 jeanne: harder to type on mobile phone 16:21:46 kp: what should we say? 16:23:22 jan: in general not bugging people for info site can determine. 16:23:44 kp: Siri knows who you are -- is there more information that can be automatic 16:25:06 detlev: issue could exist with information that is filled in incorrectly or info user doesn't want. 16:27:21 ja: may allow option to choose from list of choices rather than requiring keyboard input 16:27:37 kp: d3 support characteristics of platform 16:28:43 jan: if you have access to check capabilities follow them 16:29:00 jeanne: only recently custom fonts access was made available. 16:29:43 detlev: font resizing varies and implementation varies, a lot of differences in support 16:30:38 detlev: sometimes wrapping is handled and sometimes not. 16:32:05 kp: Does this cause a user issue? 16:32:35 detlev: users may need to use different zoom functionality, AT zoom versus pinch or text resize 16:34:01 kp: can be a stop because large percent of users can't in practice use something, e.g. issue with virtual keyboard and zooming 16:35:23 jeanne: adjust size of caption is something to add 16:36:39 detlev: can provide something on system text resize and the way it is supported 16:37:39 kp: do you want to add resize text section? 16:40:09 kp: what's different about c4 grouping related interactive elements together for mobile 16:40:42 detlev: several tab stops one element with labels and hints. 16:42:46 detlev: also issue with grouping link together -- not sure if it belongs here - practical design issue. 16:43:37 jan: a problem for desktop too 16:50:00 jeanne2 has joined #mobile-a11y 16:50:10 MichaelC_ has joined #mobile-a11y 16:55:43 Schedule: Jan 27 to WCAG WG 16:55:57 ... Feb 10, revisions back to WCAG 16:56:06 ... Feb 17, final approval 16:56:15 mc: I propose organizing the note by whatever scheme is optimal to its content, not trying to organize it around WCAG / UAAG structrue 16:56:27 also don´t restrict to advice that maps to WCAG / UAAG success criteria 16:56:40 provide your advice, map (as sufficient or advisory) where mappings exist 16:56:55 what doesn´t map is a gap, and that´s input into a guidelines gap analysis for future work 16:57:30 s/structrue/structure/ 17:02:35 -Brent 17:03:25 -Jan 17:03:27 -Michael_Cooper 17:03:29 -jon_avila 17:03:31 -Jeanne 17:03:33 -Detlev 17:04:42 zakim, list participants 17:04:43 As of this point the attendees have been Kim_Patch, Jeanne, Michael_Cooper, Detlev, Jan, jon_avila, +1.512.276.aaaa, Brent 17:04:54 rrsagent, make minutes 17:04:54 I have made the request to generate http://www.w3.org/2014/12/18-mobile-a11y-minutes.html Kim 17:07:01 -Kim_Patch 17:07:03 WAI_MATF()11:00AM has ended 17:07:03 Attendees were Kim_Patch, Jeanne, Michael_Cooper, Detlev, Jan, jon_avila, +1.512.276.aaaa, Brent 17:07:12 rrsagent, bye 17:07:12 I see no action items