14:54:24 RRSAgent has joined #views 14:54:28 logging to https://www.w3.org/2024/09/25-views-irc 14:54:28 RRSAgent, do not leave 14:54:29 RRSAgent, make logs public 14:54:30 Meeting: Defining views 14:54:30 Chair: Jan Jaap de Groot 14:54:30 Agenda: https://github.com/w3c/tpac2024-breakouts/issues/46 14:54:30 Zakim has joined #views 14:54:31 Zakim, clear agenda 14:54:31 agenda cleared 14:54:31 Zakim, agenda+ Pick a scribe 14:54:33 agendum 1 added 14:54:33 Zakim, agenda+ Reminders: code of conduct, health policies, recorded session policy 14:54:33 agendum 2 added 14:54:33 Zakim, agenda+ Goal of this session 14:54:34 agendum 3 added 14:54:35 Zakim, agenda+ Discussion 14:54:35 agendum 4 added 14:54:35 Zakim, agenda+ Next steps / where discussion continues 14:54:36 agendum 5 added 14:54:36 tpac-breakout-bot has left #views 17:48:50 JJ5 has joined #views 17:49:02 agenda? 17:49:52 rrsagent, make minutes 17:49:53 I have made the request to generate https://www.w3.org/2024/09/25-views-minutes.html JJ5 18:08:58 JJ has joined #views 18:09:02 present+ 18:14:11 kirkwood has joined #views 18:16:10 sabidussi_marco has joined #views 18:17:13 bruce_bailey has joined #views 18:17:29 present+ 18:18:01 present+ 18:18:07 hdv has joined #views 18:18:09 kevin has joined #views 18:18:18 present+ 18:18:18 present+ 18:19:57 alastairc has joined #views 18:20:52 scribenick: hdv 18:21:01 present+ 18:21:03 JJ: today's session is about defining views 18:21:21 slides: https://janjaap.com/tpac2024/ 18:21:21 JJ: the slides are on https://janjaap.com/tpac2024 18:22:46 jeroen has joined #Views 18:23:13 [introductions] 18:23:36 JJ: we'll start with current definitions in the guidelines 18:24:09 JJ: a web page, in WCAG 2.2 is a “A non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent. Web page in WCAG 2.2 ” 18:24:28 JJ: in WCAG 3, it's “Views include all content visually and programmatically available without a substantive change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content – such as a modal. ” 18:25:07 JJ: then in WCAG2ICT, there is also a definition that applies to non-web context 18:26:22 JJ: the equivalent unit of conformance for non web content is a single document, so set of web pages would be a set of documents, but then a piece of non-web software into pieces isn't possible, so 'web page'. becomes 'software program' and 'set of web paegs' becomes 'set of software programs' 18:26:40 present+ 18:26:42 JJ: in this session I want to see if we can get closer to carving up software into screens or views 18:26:50 JJ: that would allow us to have a set of screens 18:27:10 s/have a set of screens/speak of 'set of screens' 18:27:19 RRSAgent, draft minutes please 18:27:20 I have made the request to generate https://www.w3.org/2024/09/25-views-minutes.html hdv 18:27:44 JJ: in WCAG2ICT, there are a number of notes under the 'set of software program' heading 18:28:02 JJ: first note says 'set of software programs' is rare 18:29:01 JJ: because there is many notes and exceptions, in my view we'd almost never speak of a set of software programs 18:29:33 JJ: in software like the office suite, that comprises of Word, Excel etc, would that be set software programs? in my opinion it would not 18:29:40 q+ to ask about office suite 18:29:53 JJ: our group looked at how we would we apply those to mobile? 18:29:58 s/mobile?/mobile 18:30:23 JJ: in our group we wanted to think in terms of 'set of screens' for an app 18:31:15 JJ: there are different kinds of views in Android and iOS 18:31:35 JJ: screens can go onto or be popped off the stack 18:31:59 q? 18:32:13 JJ: in a website there is usually a homepage, with sub pages and sub pages underneath, so there is hierarchy 18:32:28 JJ: on an app, there are activities 18:32:36 q+ Chuck 18:33:16 JJ: so my main question is: how should we define views? and define parts of the screen like we devide parts of web sites? 18:33:16 ack me 18:33:16 hdv, you wanted to ask about office suite 18:33:17 ack hdv 18:33:22 scribe+ 18:33:35 hdv: Just about the Office suite, that is not a set of programs? 18:34:02 JJ: As far as I understand because it is not able to switch between them such as opening an Excel file in Word 18:34:08 hdv: Other examples? 18:34:24 JJ: I have not seen a real world example of a set of software that would meet this 18:34:33 hdv: Do we know where this came from? 18:34:41 JJ: Not sure 18:34:51 q+ to ask about using a concept similar to an starting point (UIcontroller, webpage etc). For example, a view is "a set of features that are all available from the same starting point, without transitioning to a completely new context." 18:35:23 ... Some things are slightly different in software. It is odd to me that there is no real world example 18:35:31 ack chu 18:35:37 scribe- 18:35:44 chuck: I have limited knowledge of the institutional history of WCAG2ICT 18:36:07 chuck: I believe in the current group the definition was heavily influenced by what's in the original note 18:36:49 chuck: the charter didn't give us a lot of space to change a lot of the existing stuff in WCAG2ICT and focused mostly on embedding the new success criteria 18:37:23 q? 18:37:41 JJ: on GitHub it seems people mostly agreed on wanting to change to set of views rather than sets of software, but it would be hard to define views in a way that works in non-web contexts 18:37:42 ack alastairc 18:37:42 alastairc, you wanted to ask about using a concept similar to an starting point (UIcontroller, webpage etc). For example, a view is "a set of features that are all available from 18:37:46 ... the same starting point, without transitioning to a completely new context." 18:37:57 alastairc: this is an important one to get a definition of 18:38:04 alastairc: as it is widely used 18:38:18 +1 to alastair regarding importance / need 18:38:45 alastairc: inspired by the diagrams you showed, I wondered if we used something as a starting point, could we define a view something like 'set of views that start from the same starting point' 18:39:18 alastairc: what I've always found difficult with web page definition and related things, whenever you get modal dialogs or bottom sheets on mobile, you get things that appear over the top, but you're still in the same context 18:39:35 JJ: I think tree view would help to show hierarchy 18:39:53 q? 18:40:06 JJ: on Android/iOS a popup still shows in the same window 18:40:13 JJ: and also traps focus 18:40:35 JJ: and similar to how desktop software would work when you show an alert of bottom sheet 18:40:54 q+ 18:41:06 JJ: when is something considered a view vs when is a substantial change? eg when you go to next view, that's quite clear but defining it is hard 18:41:14 ack alastairc 18:41:27 +1 to substantive change a design document incorporates it. 18:41:38 alastairc: a way to find out what's in scope and what's out when you're creating a definition, is to gather examples 18:42:03 alastairc: find the obvious examples of what's in and out of scope, and then find as many niche in between cases that you can 18:42:44 JJ: was thinking, if you would move between views you can usually use a back button to go back, that might be part of the definition we're looking for 18:42:46 q+ 18:42:51 ack kevin 18:43:02 UX documentation often has language regarding this 18:43:21 Francis_Storr has joined #views 18:43:30 kevin: I'm not sure if you're looking for a definition that is programmatical… from an assessment point of view you might not know what is underlying… maybe this highly depends on context? 18:43:36 JJ: agreed 18:43:54 q+ on process vs views 18:43:55 JJ: maybe there is something there like a going back/forward mechanism 18:44:10 q+ chuck 18:44:21 ack alastairc 18:44:21 alastairc, you wanted to comment on process vs views 18:44:47 alastairc: in terms of forward and back… is one useful indicator… in WCAG 3, we've got to 4 levels: component, view, task flow / process and product 18:44:56 alastairc: they are used in scoping and conformance and so forth 18:45:08 q- chuck 18:45:15 alastairc: not sure how widely applicable forward/back is across different technologies, eg thinking epub and WebVR… it's an indicator but not the whole thing 18:45:51 kevin: re forward/back, is good as a baseline if we find and define the edge cases around that 18:46:01 What if you go to a new context but there isn't (intentionally) a back? 18:46:29 JJ: in my experience, auditing an app, I only have processes, almost no screens in an app or software are standalone 18:46:40 q+ 18:46:54 JJ: would be interesting to explore some edge cases 18:47:03 ack hdv 18:47:13 scribe+ 18:47:19 hdv: Just thinking that when you follow WCAG-EM you gather pages for a sample 18:47:26 scribe- 18:47:31 ... If I think about gathering views, I wonder how much there is in the view 18:47:43 q+ on tab bars 18:47:43 ... Views in apps could be quite small steps 18:47:49 +1 to the small steps 18:48:09 ... I feel that there is something like how useful this is as a definition for an assessment 18:49:11 dotproto has joined #views 18:49:31 hdv: If you were sampling apps would you be using this definition... eg, with WCAG EM 18:49:48 kevin: wa thinking the same for a lot of apps, a single question could be a view and you'd have many similar ones 18:50:02 chuck: re defining a view… does each view have its own title? 18:50:28 JJ: not always… in apps we'd talk about a screen which has one or more screens… the top bar would have a title and actions 18:50:35 JJ: and underneath there is a scrollable container 18:50:57 JJ: so usually on a screen you would have a title, but not always 18:51:56 kevin: we spoke a few months ago about updating WCAG-EM, would we look at using this new definition to inform an update of WCAG-EM? 18:52:02 JJ: maybe like WCAGICT-EM 18:52:05 q? 18:52:20 ack alastairc 18:52:20 alastairc, you wanted to comment on tab bars 18:52:54 alastairc: going back to that JJ mentioned most apps are like a back/forward process… a lot of apps have a tab view whicih is kind of like a starting point, like a tab bar at the bottom, each starts its own set of features/functionality, whicih would be the basis for revieq 18:53:00 s/revieq/review 18:53:09 we used to call them simply layouts… later called them [UX) Layouts. this is based in print though 18:53:26 Rachael has joined #views 18:53:41 alastairc: I mentioned gathering examples… one place where I saw a good way of visualising it, designers create big flows in Figma, I couldn't supply one of my client's ones, but if we had a set of those, you could almost start drawing which chunks constitute a view 18:53:50 alastairc: that might help as an exercise 18:54:01 q+ 18:54:37 ack kirkwood 18:55:25 kirkwood: I think of what we always used to use… the old terminology, we're still using, layout as in print pages… when the layout changed and there was a significant change in the layout then that woulld be something to be approved by the design team 18:55:43 kirkwood: that might give us some structure 18:55:53 q+ 18:56:14 ack Francis_Storr 18:56:31 sabidussi_marco has joined #views 18:56:57 Francis_Storr: similar line to kirkwood… there is many things that can change on a page, so coming up with a definition of a view and then defining what other things are, eg states on a page… eg WCAG 3 talks about states and layers 18:57:07 Francis_Storr: or a different tab in a tab panel, are they different states in the view 18:57:15 q+ on the continuum 18:57:18 Francis_Storr: views are important, but what do we call those other things? 18:57:33 q+ 18:58:36 JJ: feel the same logic would apply, eg if you restore state does that also update url fragment? 18:59:09 s/, eg if you restore state does that also update url fragment?// 18:59:12 Francis_Storr: eg if you restore state does that also update url fragment? 18:59:22 JJ: if I'd navigate between a tab I would represent it in the URL 19:00:34 https://www.w3.org/TR/wcag-3.0/#dfn-views 19:00:39 alastairc: we're in that horrible position to define a line on a continuum, if you have a screen open and you have a dropdown, that's not a new view… but if you open a small popover to add an image in a document, that's prob not a new context, but a modal, is that a new view (seems like in WCAG 3 that would be a new view) 19:01:05 alastairc: there are also horrible sites that are a bit like a carousel but each arrow takes you to a new page… could be one page or multiple 19:01:10 this is a very, very significant concept! from the COGA accessibility is the change in ‘view’ causing the loss of context and getting back to view and with it is ‘unfamiliar’ and thus losing orientation. 19:01:12 alastairc: we're trying to define a point on a continuum 19:01:31 JJ: existenceo of a back button would help 19:01:31 ack alastairc 19:01:31 alastairc, you wanted to comment on the continuum 19:01:31 q+ 19:01:45 JJ: one issue on a modal you would be able to go back 19:02:43 Use of "view": Scoping the (or a) unit of conformance in WCAG 3 19:03:18 ack hdv 19:03:21 ack Rachael 19:03:28 hdv: maybe what we need to define or leave undefined can be informed by where it is used, eg views might need to be used for WCAG-EM, other terms may not be used testing any criteria so we cna leave them undefined 19:03:55 q+ 19:03:57 Rachael: what about content that is repetitive but not on the same page eg in tabs? 19:04:08 q+ to answer hdv's question 19:04:08 ack kirk 19:04:22 kirkwood: this is just an important concept from the COGA perspective 19:04:33 dotproto has joined #views 19:04:53 kirkwood: the aspect of changing view and getting lost in a view, not understanding how to go back… it's something we're trying to get our arms around with defining a lot of things that you're talking about too 19:05:27 kirkwood: maybe some of these things can be collaborated on with the COGA TF as some of these things can really break a11y for visual orientation and memory purposes 19:05:38 JJ: would be great to collaborate and see previous work 19:05:43 q? 19:05:50 ack al 19:05:50 alastairc, you wanted to answer hdv's question 19:05:50 ack alastairc 19:06:08 alastairc: re Hidde's question: this is a unit of conformance for WCAG 3 19:06:18 alastairc: trying to be more accomodating to modern web and non-web context 19:06:39 alastairc: thinking about next steps… if we were doing a subgroup on a guideline we'd start a google doc and capturing screenshots and different examples 19:06:48 alastairc: and use that to poke on proposed definition 19:06:58 alastairc: is it worth doing that? 19:07:02 JJ: good idea 19:07:26 JJ: can get examples from apps, other non ICT and also web 19:07:30 q+ 19:07:38 scribe+ 19:07:40 chuck: +q 19:08:00 hdv: In the WCAG3 space, would that delay it going into WCAG-EM 19:08:08 s/+q/+1 19:08:26 JJ: we can probably take it back to WCAG2ICT? maybe 19:08:28 q+ chuck 19:08:31 ack chuck 19:08:31 ack me 19:08:58 chuck: chatted to Kevin re this, there are some things needing to be discussed, also non-technical things, we need to have some conversations first 19:09:18 JJ: so would wonder if WCAG3 subgroup is the right forum 19:09:38 alastairc: WCAG3 is very active, but WCAG2ICT is not as active 19:09:45 JJ: but they are still going to work on AAA 19:10:03 s/WCAG2ICT is not as active/WCAG2ICT is in final stages of their publication. 19:10:50 JJ: would be great if updating 'sets of views' could be part of their updates potentially 19:10:55 alastairc: all of these TFs run under the AG banner anyway 19:11:00 q? 19:11:50 JJ: to summarise, we can explore back/forward, view changes, and maybe look at setting up a subgroup to try and research this definition 19:12:08 JJ: to make a document to showcase these views across a wide range of things 19:12:28 hdv: I'd be happy to help with that 19:13:23 RRSAgent, make minutes please 19:13:25 I have made the request to generate https://www.w3.org/2024/09/25-views-minutes.html hdv 19:13:31 Thank you for a good conversation. 19:13:36 Zakim, end meeting please 19:13:36 As of this point the attendees have been JJ, bruce_bailey, sabidussi_marco, hdv, kevin, alastairc, kirkwood 19:13:38 RRSAgent, please draft minutes 19:13:40 I have made the request to generate https://www.w3.org/2024/09/25-views-minutes.html Zakim 19:13:46 I am happy to have been of service, hdv; please remember to excuse RRSAgent. Goodbye 19:13:46 present+ Jeroen 19:13:47 Zakim has left #views 19:17:24 Francis_Storr has joined #views 19:35:09 kirkwood has joined #views 19:46:05 Francis_Storr has joined #views 20:39:40 There is a small note on right-to-repair in the CG's guidelines: https://w3c.github.io/sustyweb/#include-e-waste-right-to-repair-and-recycling-policies 23:19:40 kirkwood has joined #views 23:20:26 Francis_Storr has joined #views 23:57:01 kirkwood has joined #views