13:03:09 RRSAgent has joined #wcag2ict 13:03:14 logging to https://www.w3.org/2023/04/21-wcag2ict-irc 13:03:14 RRSAgent, make logs Public 13:03:15 please title this meeting ("meeting: ..."), dmontalvo 13:03:33 present+ 13:03:34 mitch11 has joined #wcag2ict 13:03:40 scribe: dmontalvo 13:03:44 q+ 13:04:03 q? 13:04:16 ack janina 13:04:22 Topic: First thoughts on terminal applications 13:04:36 Janina: JAson was an editor in the previous document 13:04:43 ... The two sections that are there are the result of that work 13:04:55 ... I think we want to talk about how much of that needs to be updated 13:05:09 ... I think there is also the topic of whether they are additional SC that pertain to this 13:05:42 MJ: A third one is whether there are problems or things that might not make sense to apply in this context given new SC 2.1 and 2.2 13:05:51 q+ 13:05:56 Janina: That's on my mind too. Haven't done that work yet 13:05:57 ack jasonjgw 13:06:10 Jason: I think that is an importat step to try 13:06:27 ... Ther's nothing said about the innterpretation of the existing SCs in that context, it's just about the broad principles 13:06:46 ... If there is anything that should be said that is more specific, we should do it 13:07:10 ... We should take issues that are not related to WCAG elsewhere, not clear where though 13:07:17 Janina: I'd say that's APA's responsibility 13:07:39 ... If it's not WCAG, it should be APA 13:07:48 Matthew: Sounds like it's a good fit 13:07:58 Jason: IF there are web based terminals now that's another thing 13:08:38 ... The appendix says something about the accessibility of the application that is different from the accessibility of the terminal itself 13:09:36 MJ: If we find gaps that need to be resolve, we are not the group to act on them at this point. We are now focusing on how WCAG apply to this context 13:09:48 Janina: I agree, thank you for saying it 13:10:20 ... I do think we need to look at the whole range to decide what needs and does not need to be coveredwhawt 13:10:26 Topic: What needs updating? 13:11:04 q+ 13:11:18 Janina: Command line users were treated as fossil. Glad that this was taken up at the beginning 13:11:52 ... These are no longer historical, they are now under active development, Chat GPT is an example of a "new terminal" concept, and there are many others 13:12:37 ... There ar etechincal things, like references to ASCII 13:12:53 ... Nowadays you can do much broader of a charset 13:13:10 ... There are Coga implication 13:14:00 ... There is now new concepts that have reinvented the terminal 13:14:09 ... Latency matters, but I am not sure if that's on WCAG 13:14:30 ... By databasing the interface they made it possible to build a terminal interface that is context-sensitive 13:14:58 ... Massively improve the user experience, for example checking a man page 13:15:35 ... I talked to Lissa about it 13:15:44 q+ 13:15:55 ... They may benefit from use of gh-cli 13:16:37 ... The reason why terminal is revived is because it is know much more context-sensitive 13:17:07 MJ: What's the WCAG context for this? 13:17:28 Janina: Maybe not calling it historical anymore. That framing is not accurate 13:18:16 ack mitch 13:18:57 Mit: I love the background. What's the scope? Things that run in terminal applications is clear to me 13:19:11 Either command line or full screen text-based 13:19:39 ... When we say just text-based I am not so clear 13:20:02 ... I thikn that is a rather different thing 13:20:27 MJ: I was thinking of terminal applications 13:20:45 Janina: All we had at the time was the search command 13:20:56 ... I was putting it out as a question 13:21:02 ack jasonjgw 13:21:37 Jason: That is an interesting open question, there are tools that let you run these things in a termianal 13:22:26 ... I know the existing text tries to distinguish the accessibility of the programs and that of what is running those programs 13:22:52 ... I think it is definitely true that automatic shell completion is now much more significant these days 13:23:13 q+ 13:23:18 ... Not sure how much these fit into WCAG though 13:23:35 ack matatk 13:23:52 Matthew: I think it'd be a good idea for us to define this distinction in the document 13:24:06 ... First attempt was Text/command line 13:24:15 ... These were basically things that run in a terminal 13:24:49 ... IF we are thinking of applications where text is he user interface we should make it clear too 13:24:58 ... That may be part of the revision 13:25:07 q+ 13:25:53 ... I know you can't directly apply 1.4.10 to terminal, but there is an aknowledgment that people may have many terminal windows opened 13:26:09 ... There should be the ability for these to adapt to different viewports 13:26:39 ack jasonjgw 13:27:13 Jason: The scope of this work is for non-web ICT, 13:27:53 ... What if there is a website tool that is runinng a terminal that is connected to a secure shell that's also connected to another termianal 13:28:00 q+ 13:28:10 ... Ultimately the web should be accessible but there are implication in the other parts as well 13:28:29 ... so we should be looking at the accessibility of those as well 13:29:26 q+ 13:29:39 ... Certain commands have built-in options to pipe the output in a way that it matches the given window size 13:29:40 ack mitch 13:30:06 q+ re 1.1.1, 1.4.1, 2.3.1 13:30:10 Mitch: I'd choose that the scope be things that run in a terminal 13:30:50 ... We are talking about content and applications, so it make sense to talk about them as if they are just ext, no controls or other ways of interaction 13:31:15 ... We may need to also qualify the other ways of interaction to be clear about scope 13:31:45 ... I don't know to what extent we should address web-based terminals 13:32:13 ... These are webs that would fall under WCAG, but they are also runnig "just text" so it is difficult to make that distinction 13:32:53 ack janina 13:33:00 ... There are differences in screen reader behavior between native web and native terminal, how much of these should be covered? 13:33:28 Janina: That is a good principle, and a good waay to distinguish things. Not every terminal app has controls you can click/press to activate 13:33:47 ... For all the other switchers it all depends on your environment 13:34:20 ... I am going to look if we have something on WCAG that kills the way some manufacturers do terminals 13:34:28 ... Probably we don't have it covered 13:34:52 s/manufacturers do terminals/manufacturers do terminals - redrawing the whole screen on every keypress/ 13:35:06 ... Some WCAG application is the ability to select the content that is being displayed 13:35:38 s/Not every terminal app has controls/Every terminal app does not have controls/ 13:35:50 ... How do you do your system logs as an engineer? I have only done it through the command line, I know that there are graph tools etc 13:35:53 q? 13:36:25 ack matatk 13:36:25 matatk, you wanted to discuss 1.1.1, 1.4.1, 2.3.1 13:36:27 ... This exist, so I want us to make sure we think of those 13:36:55 Matt: 1.1.1 and 1.4.1 I mentioned those in the notes I sent earlier 13:37:46 q+ 13:37:57 ... Flashing may be an issue. If you have a huge file even if it is just ext, the screen would flash. Not sure to which degree that is dangerous, but we need to look at it to see if we can include wording for the terminals to have the ability to disable this behavior 13:38:18 ack jasonjgw 13:38:45 Jason: This is a good example of it. 13:39:03 ... Basic accessibility requirement is that everything be operated via keyboard. Some of thes graphical terminals do not meet this 13:39:37 ... If they do, not sure how accessible these will be for a screen reader user 13:40:02 ... Selecting, copying, and pasting text is also an issue 13:40:41 MJ: We will have to lookat terminal applications to check which of these SC are problematic 13:40:52 Jason: Some may be already covered by existing SC 13:41:10 MJ: I am talking about the non-web terminal applications. Web-based should meet WCAG 13:41:16 q+ wrt terminal apps, checking on defintion of widgets/controls 13:41:29 q+ wrt terminal apps and checking on defintion of widgets/controls 13:41:38 q+ ;-) 13:41:40 Jason: They would have to satisfy if the web needs to comply to policies and such 13:41:51 q+ 13:41:53 ... That does not mean there's no gaps in these types of applications 13:42:04 ack ;-) 13:42:27 ... Those gaps are probably out of scope for this discussion though. 13:42:40 MJ: Not saying this is not an issue, just saying that there's WCAG for that 13:42:49 ... IF there is a missing criteria that should be outside 13:43:09 Janina: We mean WCAG3, then 13:43:22 ack mat 13:43:24 ... Which will not happen in a few years 13:44:37 Matt: I've seen a lot of developments that could be fantastic if they were exposed in an accessible way 13:44:50 q+ 13:45:36 ... I think we would still count a pseudo control like a text box maid of icon symbols as textarea 13:46:02 ... Sometimes we exempt a platform because there is no accessibility support 13:46:15 ... In mobile apps you could not do headings, now you can 13:46:50 ack mitch 13:46:51 ... IF you have a web-based terminal and you run an unmodified command terminal it is not going to take advantage of the platform, that should be noted as a caveat 13:47:33 Mitch: Back to the control question, I corrected scribe as I think it was not reflecting what Janina said 13:48:16 Janina: The controls may not be constructed into widgets 13:49:00 Mitch: This reminds me of 1.3.1 language but 4.1.2 does not have that language 13:49:10 q? 13:49:24 Topic: Next Steps 13:49:42 MJ: How do we want to work? What are next steps? 13:50:09 ... It sounds like there are some smaller content changes that need to happen, we should be clearer about the scope 13:50:18 ... We may need to make some technical changes as well 13:50:40 ... The appendix goes into further detail but it does not get into the analysis of each SC 13:51:43 Matthew: What we have discussing could be considered a patch for terminal applications, sounds like reasonable next steps 13:51:49 ... Happy to help 13:52:10 JAnina: I would volunteer to take a pass at the summary section 13:52:32 ... On the appendix I think we should be able to say Yes, No, Maybe, for each of them 13:52:51 Jason: I'd volunteer to participate 13:52:56 Mitch: Me too 13:53:16 Janina: We cannot change anything it says. These changes need to be WCAG3 13:53:45 MJ: How should we work on tihs? 13:54:13 Janina: Happy to create and ASCII spreadsheet 13:54:25 MJ: I can then turn this into a spreadsheet 13:54:56 Matt: I loved Mitchell's calling terminal applications "user agents" 13:55:16 ... I think we should include this somewhere 13:55:23 MJ: When should we get back together? 13:55:57 Janina: Two weeks from today would be 5 May 13:56:10 Janina: It works for me 13:56:22 Mitch: Sounds good to me 13:57:00 MJ: We have tasks to do, we can email ourselves, Janina, when you have the spreadsheet please send it my way, let's try to have something together a couple of days before the meeting. 13:57:21 ... Everyone please by 3 May get things to me 13:57:33 q+ 13:57:48 rrsagent, draft minutes 13:57:49 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html dmontalvo 13:59:41 Meeting: WCAG2ICT terminal applications 13:59:53 Chair: Mary Jo 13:59:54 rrsagent, make minutes 13:59:55 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html matatk 14:00:01 rrsagent, draft minutes 14:00:02 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html dmontalvo 14:00:35 jasonjgw has left #wcag2ict 14:08:05 s/Chat GPT is an example of a "new terminal" concept, and there are many others/there are many "new terminal" concepts these days/ 14:08:12 rrsagent, draft minutes 14:08:14 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html dmontalvo 14:51:45 present+ 14:52:01 rrsagent, make minutes 14:52:03 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html maryjom 14:53:45 present+ Mitch, dmontalvo, matatk, jasonjgw 14:53:57 rrsagent, make minutes 14:53:58 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html maryjom 14:55:52 s/thes /these/ 14:57:11 s/create and/create an/ 14:57:52 s/email ourselves/email between us/ 14:59:02 rrsagent, make minutes 14:59:03 I have made the request to generate https://www.w3.org/2023/04/21-wcag2ict-minutes.html maryjom 15:34:26 maryjom has joined #wcag2ict 15:48:59 maryjom has joined #wcag2ict 17:55:02 Zakim has left #wcag2ict