15:02:12 RRSAgent has joined #mobile-a11y 15:02:12 logging to http://www.w3.org/2016/09/01-mobile-a11y-irc 15:02:14 RRSAgent, make logs public 15:02:15 Zakim has joined #mobile-a11y 15:02:16 Zakim, this will be WAI_MATF 15:02:16 ok, trackbot 15:02:17 Meeting: Mobile Accessibility Task Force Teleconference 15:02:17 Date: 01 September 2016 15:02:25 zakim, this will be 6283 15:02:26 ok, Kathy_ 15:02:44 meeting: Mobile A11Y TF 15:02:55 chair: Kathy 15:03:13 Jatin has joined #mobile-a11y 15:03:17 Scribe: Detlev 15:03:32 Kathy: We are behind schedule 15:03:36 patrick_h_lauke has joined #mobile-a11y 15:03:46 present+ patrick_h_lauke 15:03:49 KW: Have to do one per week 15:04:02 present+ Detlev 15:04:07 present+ Jatin 15:04:26 dmacdona has joined #mobile-a11y 15:04:33 KW: Please respond to emails asking for feedback for finalising SCs 15:04:38 (early warning: need to duck out early from this call for childminding) 15:04:47 KW: Your feedback is critical 15:05:11 present+ davidmacdonald 15:05:25 KW: Have to finalise Accidental activation and touch target today - othwerwise will be finalised on list 15:05:40 kim has joined #mobile-a11y 15:05:43 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3 15:05:55 KW: Last week we made revisions to Accidental activation SC 15:07:01 DMD: We need the language of the SC itself - many things can be revised later, like examples and benefits 15:07:27 DMD: Broad strokes most important 15:07:37 KW: But get language right 15:08:09 KW: Any concerns regarding other aspects of SC (benefits etc.)? 15:08:20 chriscm has joined #mobile-a11y 15:08:38 KW: Not going back to SCs that have already been sent to WCAG WG 15:08:54 KW: Focus on Accidental activation and touc htarget today 15:09:01 KW: Any comments? 15:09:16 KW: Consider this final? 15:09:32 DMD: Note should be added to collect feedback 15:10:30 KW: Resolution: SC No Accidental Activation has been accepted, ready for WG review 15:10:48 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Target_Size 15:11:01 KW: Next one is Touch Target Size 15:11:35 KW: A lot of back and fortth, changes, info on evidence, diverging recommendation 15:12:07 KW: Question to input sizes for touch and mouse/pencil activation 15:12:29 KW: Please read SC text no, for a few miutes, then let's discuss 15:12:55 jon_avila has joined #mobile-a11y 15:13:01 present+jon_avila 15:13:24 KW: Comments on coarse and fine pointing accuracy? 15:14:31 PL: As commented research papers have a lot of grey areas - studies were in controlled environments with fixed size screens - our issue is that we don't know usera' device size 15:14:54 PL: That's why we focus on CSS pixels 15:15:56 PL: Size for web buttons on small mobile devices may be excessive - viewing distance should be taken into account (closer usually with phones, so larger relative size) 15:16:27 PL: Research is interesting but data from Apple / Google / Microsift guidance possibly more relevant 15:17:05 PL: Apple goes for 44 (like BBC), Google goes for 48 px - 50 would be a round number 15:17:18 present+ marcjohlic 15:17:54 PL: We just pickled 20 px with no clear guidance, could make it 25 px (half od large pointer target size) 15:17:58 q* 15:18:01 q+ 15:18:52 CM: does 24 / 46 make sense if ratio / scaling od CSS pixels is added? 15:19:06 LP: Depends on dpi of device 15:19:42 q+ 15:20:03 getting lots of interference on the line 15:20:26 i'm call-in 3 and am muted 15:20:57 detlev might be your line 15:22:31 q+ 15:23:13 q- 15:23:14 PL: 44 px is a good value - the issue with too little buttons on screen referred to a much larger value (150 px) 15:24:10 50's good for me 15:24:20 KW: MIT study arrived at 44-57 px - my preference would be at the higher end, say 50 px 15:24:33 DMD: agrees 15:25:06 DMD: Better to start with a larger requirement and then reduce it in negotiations than the othe rway round 15:26:09 50 / 26 15:26:16 PL: different terms effective pixes, density pixels all map onto CSS pixels 15:26:20 +1 50 and 26 15:26:28 +1 50 and 26 15:26:35 KW: Any objections to 50 / 25 pixels? 15:27:09 DO we want 26 or 25 for the small? 15:27:31 MJ: The most relaible thing woulf be using actual millimeters but we have no way of measuring it across devices - hopes that manufactures CSS calculations are correct 15:28:08 PL: usinf CSS pixels will be more accurate because there is no way of testing it across devices 15:28:36 MJ: Similar issue with contraast, actual screen contrast on different devices 15:28:56 PL: Same way device differences cannot be factored in 15:29:23 KP: does it more sense to pick 24/28 px? 15:30:21 CM: No technical reason to pick one over the other - would there be less pushback if measures match Google's suggestion? 15:31:17 KW: We have some evidence from research that larger target sizes make things easier - device manufacturers have different values anyway - so we cab just as well round to 50 15:32:04 PL: Problem migh rtbe that 48 would already fail where Google suggests the nearly identical 49 px could be annoying 15:32:11 DMD agrees 15:32:41 KW; that happened with color contrast, ISO standard slightly lower 15:32:57 +1 to 48 as our starting point 15:33:00 CM: Developers would leave ot at 48 if 50 is required 15:34:55 detsiled calculations of pix vs. mm conversions, too much to script) 15:35:45 PL: difference betwee 50 and 48 px is less than .4 mm 15:35:55 24/48 15:36:04 +1 48 and 24 15:36:05 +1 48 and 24 15:36:11 +1 48 and 24 15:36:21 q+ to talk about "CSS pixel" definition 15:36:25 +1 15:36:31 Resolution: target size is 48 and 24 px 15:36:59 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Target_Size 15:37:27 KW: Change to definition of CSS pixels under Related Glossary additions or changes - please have a look nw 15:37:34 yeah current definition is slightly back-to-front 15:37:46 q? 15:37:52 q- 15:38:17 q+ 15:39:18 PL: CSS pixel definiton should have addition in brackets (when the page is using the device'S ideal viewpoint) 15:39:39 viewport, not viewpoint 15:39:53 https://www.w3.org/TR/CSS2/ 15:39:59 PL: pointer spec references CSS spec 15:40:36 PL: should not be defined sepearately but part of the SC text 15:40:41 https://www.w3.org/TR/pointerevents/ 15:41:34 KW: Changes text / definition 15:42:41 CM: for natiove apps CSS px is useless - there are conversions though 15:43:26 KW: Focus is web stuff now - if applied to nave there would be more about conversion to native environments 15:43:48 PL: A note could be added to point to the resp. native environments and their terminologies 15:44:56 KW: Description, evidence, examples, testability (new) - may be change to ideal viewport needed? 15:45:02 PL: makes sense 15:46:06 PL: Question about "larger than vs. larger or equal to" 15:46:12 KW (changes text) 15:46:32 KW: Any other changes needed? 15:47:01 KW: Can we finalise this? 15:47:02 ship it! 15:47:07 +1 15:47:11 agree 15:47:45 Resolution: SC Target Size is accepted 15:47:53 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements 15:48:08 KW: Schedule for SC submission 15:48:19 shadi has joined #mobile-a11y 15:48:24 KW: Kim is working on Speech SC 15:48:51 KW: PL is working on several - need to reassign work? 15:49:37 KP: Three SC on speech - feedback is welcome, mail Kim 15:50:32 KP: it's M12 15:50:39 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements 15:50:40 KW: M12 is empty 15:51:19 KP: On main wiki page - 15:51:25 KW: put on timeline document 15:51:30 shadi has joined #mobile-a11y 15:52:16 KW: Patrick - split soemtzhing off? Will chat to Detlev Chris 15:52:27 I can pick something up 15:53:09 KW: Will package the ones now agreed 15:53:59 PL: There were questions on WCG WG call about touch with AT on - comment it might be too specific, reference to desktop / keyboard with AT on 15:54:36 PL: Wonders whether it is worth merging the Touch + AT and Keyboard + AT to a more generic SC 15:55:12 KW: We shoulf stick with what we have now, can be merged later by WG 15:55:39 KW: First get feedback, then revisit after Dec 1 15:56:19 KW: closes call 15:56:29 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.0_Techniques_Applicable_to_Mobile_without_Changes 15:57:00 need to shoot off 15:57:04 patrick_h_lauke has left #mobile-a11y 15:57:10 Jatin: Looking for a technique for mobile accessibility ? (not fully understood by scibe) 15:57:20 https://www.w3.org/WAI/GL/mobile-a11y-tf/MobileTechniques/ 15:57:35 https://www.w3.org/TR/mobile-accessibility-mapping/ 15:57:43 Jatin: Applicable to native mobile? 15:58:11 KW: respective applicability should be visible on techniques 15:59:40 zakim, list attendees 15:59:40 As of this point the attendees have been patrick_h_lauke, Detlev, Jatin, davidmacdonald, jon_avila, marcjohlic 15:59:53 rrsagent, make minutes 15:59:53 I have made the request to generate http://www.w3.org/2016/09/01-mobile-a11y-minutes.html Kathy_ 16:00:04 rrsagent, make logs public 17:01:46 chriscm has joined #mobile-a11y 18:03:09 Zakim has left #mobile-a11y 19:00:04 chriscm has joined #mobile-a11y 20:03:54 chriscm has joined #mobile-a11y 21:04:41 chriscm has joined #mobile-a11y 22:05:29 chriscm has joined #mobile-a11y