12:58:16 RRSAgent has joined #matf 12:58:20 logging to https://www.w3.org/2024/10/09-matf-irc 12:58:20 RRSAgent, make logs Public 12:58:21 please title this meeting ("meeting: ..."), JJ 12:58:25 Zakim, this is MATF October 9, 2024 12:58:25 got it, JJ 12:58:32 Meeting: MATF October 9, 2024 12:58:38 present+ 12:58:43 agenda+ 2.5.8 Target Size (Minimum) 12:58:51 agenda- 1 12:58:51 present+ 12:59:00 agenda+ View subgroup 12:59:06 agenda+ 2.5.8 Target Size (Minimum) 12:59:18 agenda+ 3.2.1 On Focus 12:59:22 AlainVagner has joined #matf 12:59:24 agenda+ 3.2.2 On Input 12:59:26 present+ 12:59:32 zakim, agenda? 12:59:32 I see 4 items remaining on the agenda: 12:59:33 2. View subgroup [from JJ] 12:59:33 3. 2.5.8 Target Size (Minimum) [from JJ] 12:59:33 4. 3.2.1 On Focus [from JJ] 12:59:33 5. 3.2.2 On Input [from JJ] 13:01:25 julianmka has joined #MATF 13:01:41 present+ 13:02:13 GleidsonRamos has joined #matf 13:02:16 q+ 13:02:19 present+ 13:02:42 q- 13:02:58 https://nldesignsystem.nl/events/design-systems-week-2024/en/program 13:03:33 I can scribe today 13:03:44 https://dl.acm.org/doi/10.1145/3674967 13:03:51 q+ 13:03:52 scribe: Detlev 13:04:02 ack Joe_Humbert 13:04:18 Carolina has joined #MATF 13:04:23 present + 13:04:31 Joe: article on list: Apple does research on automated a11y report generation 13:04:31 present+ 13:05:02 ...maybe the will improve the a11y of their own tool as well ;) 13:05:31 JJ: indicating extending checks to several screens 13:05:46 ... leverage AI Computer Vision 13:06:13 Joe: why do they use AI to identify objects rather than accessing the code? 13:06:26 ...code is more accurate 13:06:48 JJ: using private APIs, iphone sharing (mirror on Mac) 13:07:02 Karla has joined #matf 13:07:10 ...not yet available in EU maybe due to privacy issues 13:07:25 present+ 13:07:53 EU with regulations may open up iOS a bit more 13:08:21 q? 13:08:26 move to next agendum 13:08:26 agendum 2 -- View subgroup -- taken up [from JJ] 13:08:41 Jamie has joined #matf 13:08:52 present+ 13:09:14 JJ: forwarded Email with invitation of AGWG for the View subgroup (result of talk at TPAC about definition of view) 13:09:36 ...what does it mean in context of web page, Apps, mobile apps 13:09:43 ...may be used in WCAG 3 13:10:01 ...if interested please fill in survey w available meeting times 13:10:14 q+ 13:10:17 ...questions? 13:10:19 ack Jamie 13:11:00 Jamie: How much commitment - what is the time line - how long is it going to take compare what we do here? 13:11:16 JJ: not sure - timeline will be defined in subgroup 13:11:54 move to next agendum 13:11:54 agendum 3 -- 2.5.8 Target Size (Minimum) -- taken up [from JJ] 13:13:35 JJ: first discussion was 1 May 2024 13:13:53 JJ shares Issue from GitHub 13:14:25 JJ: Apple and Android have requirement for larger touch targets 13:14:48 JJ: explaining spacing exception in 2.5.8 13:15:30 julianmka has joined #MATF 13:15:35 present+ 13:16:02 JJ: continue discussion? 13:16:09 q? 13:16:32 q+ 13:16:40 ack Detlev 13:17:39 Detlev: go beyond WCAG (target size)? 13:18:00 JJ: stay in line with WCAG2ICT but some notes for best practices could be added 13:18:02 q+ 13:18:35 q+ 13:18:39 JJ: such as recommending larger sizes, reference developer documentation 13:19:36 ack julianmka 13:19:56 JJ: Question was whether we better align with WCAG or WCAG2ICT -- the latter was preferred 13:20:59 Julian: Tell people to choose whatever is the more accessible (eg. decide between WCAG requirement and Android/iOS recommendations). 13:21:29 q+ 13:21:43 ...Android and iOS are closed platforms where WCAG has no clout - that'S why we could instruct user sdto chosse the better one 13:21:59 JJ: could be trouble to link directly to Apple and Google 13:22:35 ack Joe_Humbert 13:23:06 Joe: we should not use could language to inform people what they *should* be doing 13:23:23 ...could is not used 13:24:03 ...we could say it is too small for touch and one could point to triple A guideline without spacing exception 13:24:50 ack Jamie 13:25:30 Jamie: as to adding Apple and Google resources: WCAG resources do include references to these 13:25:52 ..."for information purposes only" 13:26:33 ...not endorsed, but available - we could do it as well 13:27:33 ...we are talking about AA 2.5.8 - we can point to AAA as best practice - should not linger longer, this is the AA standard 13:28:02 JJ: most people felt it can be applied 'as is' 13:28:52 JJ: comfortable with accepting as such and add a note to preferability of larger sizes? 13:29:24 Add note to 2.5.8 to point people towards resources which recommend larger touch target sizes (such as WCAG 2.5.5, Apple, Google)? 13:29:34 +1 13:29:36 +1 13:29:36 +1 13:29:39 +1 13:29:41 a+ 13:29:42 +1 13:29:45 q+ 13:30:01 +1 13:30:07 +1 13:30:11 ack Jamie 13:30:12 +1 13:30:49 Jamie: We would not be using the term CSS-pixels - replace with something else 13:31:21 JJ: may be density pixels or other units that make sense 13:31:36 ACTION: Add note to 2.5.8 to point people towards resources which recommend larger touch target sizes (such as WCAG 2.5.5, Apple, Google) 13:31:55 ACTION: Replace CSS Pixel unit with appropriate unit on mobile such as Density Pixel 13:33:53 q? 13:33:58 JJ: will set up draft version of what guidance would look like 13:34:04 move to next agendum 13:34:04 agendum 4 -- 3.2.1 On Focus -- taken up [from JJ] 13:35:10 JJ: can we keep going through SCs (niot focus on medium variations as suggested by Jamie)? 13:35:32 JJ: (reads 3.2.1 On Focus and add. notes) 13:35:47 ...of WCAG2ICT 13:36:16 AlainVagner has joined #matf 13:37:08 JJ: (going through examples) 13:37:22 q+ 13:38:00 q? 13:38:04 ack Joe_Humbert 13:38:06 JJ: example that filling out second form field should not force focus to first. ANy comments? 13:38:45 Joe: WCAG2ICT did not change definition of "change of context" even things that explicitly mention "web page" 13:38:59 ...we should change the definition 13:39:36 Joe_Humbert: We need to look at user agent and viewport as well 13:41:37 JJ: Structure in WCAG2ICT can be a bit confusing - some wordign changed - but not when applied as written 13:41:44 q? 13:42:18 JJ: Can't remember why this was marked as large variation... 13:42:26 ...seems straightforward 13:42:45 q+ Jamie 13:42:47 ack Jamie 13:44:26 Jamie: wondering what the idea of focus was - keyboard focus, SR focus - in the mobile space, voice control ans switch access - do we need to differ from the description in the WCAG context - what tools create focus... that may have been the reason what we were marking it as large variation 13:45:14 JJ: define perhaps what user interface components would be - a label? 13:45:44 JJ: most work would be on the definitions (UIE, change of context) 13:45:55 ACTION: Create Github issue for User Interface Component 13:46:03 ACTION: Create Github issue for Change of Context 13:46:28 move to next agendum 13:46:28 agendum 5 -- 3.2.2 On Input -- taken up [from JJ] 13:47:09 JJ: (looking at WCAG2ICT text for 3.2.2 on input) 13:47:30 ...reading intent 13:48:16 ...looking at the MATF Github issue 13:48:23 q+ 13:48:41 ack Joe_Humbert 13:49:18 Joe_Humbert: We also need to look at the definition of user interface component, check if we need to modify that 13:49:20 q+ 13:49:33 ...what is it we think a control is? 13:49:50 q- 13:50:08 JJ: same note about user interface element 13:50:56 JJ: agenda is finnished - any additional topics? 13:51:15 Jamie: what is the next SC? 13:51:45 agenda+ 3.2.3 Consistent Navigation 13:51:46 JJ: (checking which is next - consistent navigation) 13:52:23 Joe: Should be staret a document for "proposed definitions" so we can work outside meetings? 13:52:42 ACTION: Mark Github issues related to Definitions with 'definition' tag 13:52:55 move to next agendum 13:52:55 agendum 6 -- 3.2.3 Consistent Navigation -- taken up [from JJ] 13:53:05 +1 to Joe_Humbert 13:54:00 JJ: WCAG2ICT added a note that while not required SC should be considered best practice 13:54:41 ...relates to the problematc definition to "set of software programs" (rather than "set of views") 13:55:15 q+ 13:55:25 JJ: In the EN 301 549 it is also considered to change to sets within software 13:55:28 ack Jamie 13:56:33 Jamie: If we have a note, the way it is written does not clearly stating the purpose 13:57:03 ...seems confusing right now - we should not use the same wording 13:57:18 JJ: if we can view or screen it will be clearer 13:58:02 JJ: We might need an exception because there may be valid reasons to deviate in terms of order 13:58:38 q? 13:58:46 ...need ti figure out if exception is needed - may not be needed since note is not normative 13:59:29 JJ: we may also discuss consistent help - applies more to web sites 13:59:59 JJ: will send out minutes after the meeting 14:01:16 rrsagent, make minutes 14:01:18 I have made the request to generate https://www.w3.org/2024/10/09-matf-minutes.html JJ 14:29:53 rrsagent, bye 14:29:53 I see 5 open action items saved in https://www.w3.org/2024/10/09-matf-actions.rdf : 14:29:53 ACTION: Add note to 2.5.8 to point people towards resources which recommend larger touch target sizes (such as WCAG 2.5.5, Apple, Google) [1] 14:29:53 recorded in https://www.w3.org/2024/10/09-matf-irc#T13-31-36 14:29:53 ACTION: Replace CSS Pixel unit with appropriate unit on mobile such as Density Pixel [2] 14:29:53 recorded in https://www.w3.org/2024/10/09-matf-irc#T13-31-55 14:29:53 ACTION: Create Github issue for User Interface Component [3] 14:29:53 recorded in https://www.w3.org/2024/10/09-matf-irc#T13-45-55 14:29:53 ACTION: Create Github issue for Change of Context [4] 14:29:53 recorded in https://www.w3.org/2024/10/09-matf-irc#T13-46-03 14:29:53 ACTION: Mark Github issues related to Definitions with 'definition' tag [5] 14:29:53 recorded in https://www.w3.org/2024/10/09-matf-irc#T13-52-42