20:16:12 RRSAgent has joined #matf 20:16:16 logging to https://www.w3.org/2023/12/04-matf-irc 20:16:16 RRSAgent, make logs Public 20:16:17 please title this meeting ("meeting: ..."), jj 20:16:25 present+ 20:16:35 Mick has joined #MATF 20:16:52 meeting: MATF Monday 4 December 2023 20:17:11 + 20:17:30 present+ 20:17:39 TOPIC: ACT Rules 20:18:12 Talking about the Accessibility Conformance Testing (ACT) rules for mobile 20:18:21 Some are generic, others are HTML/web specific 20:18:52 TOPIC: WCAG 2.2 mobile mapping 20:20:26 Discuss columns Applicable to mobile Web and Applicable to mobile Native, vote as task force perhaps to get an agreement? 20:22:27 Two documents: "WCAG 2.2 SC that Apply to Pure Native Mobile" and "- How WCAG 2.2 Relates to Mobile and What's Missing" - how do they differ? 20:23:04 Maybe we should merge these into one document? 20:23:44 Copy notes from 1st doc to 2nd doc at right place 20:25:40 https://w3c.github.io/Mobile-A11y-TF-Note/ vs https://www.w3.org/TR/mobile-accessibility-mapping/ 20:31:47 TOPIC: How to name "app accessibility" 20:37:05 Mick: Web mobile, native Android, native iOS, Native Mobile, differentiate between hybrid/cross-platform? 20:37:18 Mobile App Accessibility? 20:38:02 App can be downloaded from the App Store / Google Play 20:40:46 App Accessibility Task Force? AATF 20:41:01 Native Mobile Accessibility Task Force NMATF 20:41:11 Mobile App Task Force (MATF) 20:41:45 Mobile App Accessibility Task Force (MAATF) 20:44:39 Mobile app = Android/iOS? What about wearOS / watchOS? and iPadOS? etc. 20:44:58 Watch is also a mobile device 20:46:28 TOPIC: WebView / web content in apps 20:46:38 How do we deal with web views and web content inside apps? 20:46:57 Judge WEB content using default WCAG guidance? 20:48:09 What should happen with font size inside WebView? E.g. native app uses 200% font size, then the WebView should also use this scale? 20:49:37 Guidance on WebView's can help, maybe there are some exceptions or best-practices we can write about 20:50:09 TOPIC: Mapping 20:50:15 Mick: Native Android, native iOS, hybrid, cross-platform, all separately mapped? Or one version? 20:50:51 JJ: Take existing guidance from Apple/Google into account: Human Interface Guidelines & Core app quality 20:51:11 Focus on native android/ios first, then see how to fit hybrid/cross-platform/etc.? 20:51:38 Focus on platform behavior, not on framework/programming language 20:52:04 Platform expectations 20:52:39 Take existing platform accessibility requirements and consider them in the mapping 20:53:35 Touch-target size = 48x48 on Android, 44x44 on iOS, WCAG 2.2 has 24x24 at level AA, WCAG AAA has 48x48 20:54:14 Material Design also has accessibility: https://m3.material.io/foundations/accessible-design/overview 20:55:30 Core app quality: https://developer.android.com/docs/quality-guidelines/core-app-quality 20:55:50 Human Interface Guidelines: https://developer.apple.com/design/human-interface-guidelines/designing-for-ios 20:59:24 Check which requirements relate to accessibility / WCAG requirements and add those as requirement if different from WCAG 21:05:02 zakim, list participants 21:05:02 As of this point the attendees have been jj, Mick 21:05:10 rrsagent, make minutes 21:05:11 I have made the request to generate https://www.w3.org/2023/12/04-matf-minutes.html jj 21:05:47 rrsagent, bye 21:05:47 I see no action items