12:59:11 RRSAgent has joined #matf 12:59:15 logging to https://www.w3.org/2024/10/16-matf-irc 12:59:15 RRSAgent, make logs Public 12:59:16 please title this meeting ("meeting: ..."), JJ 12:59:22 Zakim, this is MATF October 16, 2024 12:59:22 got it, JJ 12:59:30 Meeting: MATF October 16, 2024 12:59:36 present+ 12:59:45 regrets+ Julian 12:59:52 regrets+ AlainVagner 12:59:56 regrets+ Karla 13:00:02 regrets+ Joe_Humbert 13:00:46 agenda+ Github Pages 13:00:52 agenda+ 3.2.3 Consistent Navigation 13:00:58 agenda+ 3.2.4 Consistent Identification 13:01:03 agenda+ 3.2.6 Consistent Help 13:01:09 agenda+ 3.3.2 Labels or Instructions 13:01:17 zakim, agenda? 13:01:17 I see 5 items remaining on the agenda: 13:01:18 1. Github Pages [from JJ] 13:01:18 2. 3.2.3 Consistent Navigation [from JJ] 13:01:18 3. 3.2.4 Consistent Identification [from JJ] 13:01:18 4. 3.2.6 Consistent Help [from JJ] 13:01:18 5. 3.3.2 Labels or Instructions [from JJ] 13:03:34 present+ jeroen 13:05:10 thnc 13:05:14 thnx 13:05:24 Mick has joined #MATF 13:05:48 Aash has joined #matf 13:06:11 present+ 13:06:16 scribe: Mick 13:06:19 present+ Mick 13:06:26 move to the next agendum 13:06:36 Zakim, move to next agendum 13:06:36 agendum 1 -- Github Pages -- taken up [from JJ] 13:08:11 Github repo: https://github.com/w3c/matf 13:08:12 JJ - Overview of Github action workflow and how index.html file is deployed. 13:08:18 Deploys at: https://w3c.github.io/matf/ 13:08:43 Devanshu has joined #matf 13:08:49 present+ 13:09:38 JJ - now we have something that we can share directly with world. Most guidance we have made is included. The goal is to align closely with WCAG2ICT 13:10:00 JJ - Can share with people in the future when we are ahead with the guidence 13:11:02 JJ - new 'meeting' label added to GitHub issues that will be discussed in meetings. 13:11:10 Zakim, move to next agendum 13:11:10 agendum 2 -- 3.2.3 Consistent Navigation -- taken up [from JJ] 13:12:08 q+ 13:12:15 JJ - WCAG2ICT replaces "set of web pages" with "a software program" 13:12:32 q- 13:13:12 JJ - correction - EN 301 549 replaces "set of web pages" with "a software program" 13:15:07 JJ - This mostly related to how we replace "set of web pages". 13:15:12 q+ 13:15:20 ack Mick 13:15:58 Mick: in our group we would look at a relatively small set of components for consistent navigations, such as search buttons? 13:16:20 q+ 13:16:57 ack Aash 13:16:57 JJ - I would consider a back button, close button, buttons in a list, a change of tab in a tab bar. 13:18:00 Aash - should we introduce certain things - the bottom sheets without the close button. Very hard to dismiss those overlays. 13:18:46 JJ - I think it would be interesting to add such things in a Note. That might be more related to Keyboard Operation rather than this success criterion 13:20:44 JJ - I wonder would a back button or close button placed differently would fail this criteria in app or is it too strict. Is it more about large lists of links rather than a single link/button. 13:20:50 Jamie has joined #matf 13:20:55 present+ 13:21:10 q+ 13:22:00 ack Jamie 13:22:22 JJ - Does 'navigational mechanisms' related to one button or link 13:23:03 Jamie - this criteria isn't about where the back button is on every app 13:23:18 q+ 13:24:05 ACTION: Define "navigational mechanisms" 13:24:12 Jamie - what are we considering navigational mechanisms? It would be helpful outlining examples. 13:25:37 JJ - this is specific to a single app. 13:26:09 ack Mick 13:28:20 Zakim, move to next agendum 13:28:20 agendum 3 -- 3.2.4 Consistent Identification -- taken up [from JJ] 13:31:26 JJ - WCAG2ICT set it to applies to a set of soft programs. EN standard set the scope from a “set of web pages” to "a software program". 13:32:18 JJ - 'same functionality' is pretty clear. 13:32:53 q+ 13:33:04 ack Jamie 13:36:26 Jamie - Components and functionality are central to this criteria. The intent outlines that consistency extends to the text alternatives. Should we clarify exactly what is included? 13:37:17 JJ - It would be helpful to define if it's specific to component or user-interface components. 13:40:11 +q 13:40:39 JJ - Is there any instance where a developer wouldn't be able to alter components. Such as if a user agent defines them. 13:40:43 ack Mick 13:41:28 q+ 13:42:02 Mick: can't think of any reason why developers wouldn't be able to do this 13:44:34 JJ - we should have some note about this success criterion, and others related around the 'set of screens' and where hybrid relates. Would all views or screens in an app be included, regardless if they are a web or hybrid view. 13:44:40 ack Jamie 13:45:39 JJ - I think that maybe in a screen or view we only consider the native app components. Maybe we exclude web. 13:46:11 Jamie - what would the logic be in excluding web views? 13:46:42 JJ - The EU standards exclude web views. WCAG itself would apply 13:46:51 q+ 13:47:46 q+ Jamie 13:47:50 ack Jamie 13:49:07 Jamie - I can see as a task force that it's helpful to separate native and hybrid but with these success criteria it impacts the user's experience. If it's the same functionality it should be consistent regardless of the underlining code. 13:50:37 ack Mick 13:51:02 ACTION: For first draft, make first version of how we deal with hybrid apps and web content in apps 13:51:57 Zakim, move to next agendum 13:51:57 agendum 4 -- 3.2.6 Consistent Help -- taken up [from JJ] 13:54:49 JJ - EN 301 549 marked this success criterion is not applicable. 13:54:54 https://labs.etsi.org/rep/HF/en301549/-/issues/278 13:59:07 q+ 13:59:10 q+ 13:59:12 ack Jamie 13:59:12 Aash has joined #matf 14:00:16 ACTION: Gather screenshots of help mechanisms in apps for next meeting 14:00:22 Jamie - be helpful to get examples of help mechanisms. 14:00:39 ack Mick 14:00:45 Zakim, close queue 14:00:45 ok, JJ, the speaker queue is closed 14:03:14 Mick - My understanding is this SC is only related to to if help mechanisms do exist on a view or screen, that they appear in the same relative programmatic order, it doesn't require them on multiple views. 14:04:08 rrsagent, make minutes 14:04:10 I have made the request to generate https://www.w3.org/2024/10/16-matf-minutes.html JJ 14:04:54 rrsagent, bye 14:04:54 I see 3 open action items saved in https://www.w3.org/2024/10/16-matf-actions.rdf : 14:04:54 ACTION: Define "navigational mechanisms" [1] 14:04:54 recorded in https://www.w3.org/2024/10/16-matf-irc#T13-24-05 14:04:54 ACTION: For first draft, make first version of how we deal with hybrid apps and web content in apps [2] 14:04:54 recorded in https://www.w3.org/2024/10/16-matf-irc#T13-51-02 14:04:54 ACTION: Gather screenshots of help mechanisms in apps for next meeting [3] 14:04:54 recorded in https://www.w3.org/2024/10/16-matf-irc#T14-00-16