16:27:44 RRSAgent has joined #waicc 16:27:48 logging to https://www.w3.org/2024/04/22-waicc-irc 16:27:48 RRSAgent, make logs Public 16:27:49 Meeting: WAI Coordination Call Teleconference 16:27:51 present: Shawn 16:27:54 Chair: Shawn 16:28:02 zakim, clear agenda 16:28:02 agenda cleared 16:28:11 agenda+ scribe to today 16:28:59 agenda+ TheLounge 16:28:59 agenda+ Updates around the table 16:30:05 janina has joined #waicc 16:30:09 agenda? 16:33:13 matatk has joined #waicc 16:33:23 present+ 16:33:31 present+ 16:33:48 scribe+ 16:33:50 zakim, drop agenda 1 16:33:50 agendum 1, scribe to today, dropped 16:33:57 scribe+ 16:34:02 zakim, next item 16:34:02 agendum 2 -- TheLounge -- taken up [from shawn] 16:35:04 https://docs.google.com/document/d/1sIErFDJMl1vpjZXmfaNksl1QE2H-Px1MGMBexZmkRAQ/edit 16:35:23 janina: COGA and AG collecting issues with TheLounge in the [above] Google Doc 16:35:42 janina: People all over the planet are getting disconnected a lot, two or three times an hour sometimes. 16:35:52 janina: Not sure if anyone's filed that issue yet (need to check). 16:36:07 ... Also there are color contrasts that don't meet WCAG. 16:36:18 ... Are these W3C implementation issues, or are they upstream issues? 16:36:33 Jem has joined #waicc 16:36:53 zakim, who is on the phone? 16:36:53 Present: Shawn, matatk, janina 16:36:58 present+ 16:37:04 present+ 16:37:14 present+ JaeunJemmaKu 16:37:27 present+ James, MaryJo, Daniel 16:37:32 zakim, who is on the phone? 16:37:32 Present: Shawn, matatk, janina, kevin, JaeunJemmaKu, James, MaryJo, Daniel 16:37:34 ... Then here's the policy issue of this being launched without any consultation/beta period - maybe not a huge deal as most feedback is good. 16:37:49 -> https://docs.google.com/document/d/1BMEOIEzKOSCsdMvOiB62o5qxQtk-mS-XGL6_HRmGodA/edit#heading=h.grjhk5tpcewl AGWG Issues 16:37:50 matatk: There was also concern about the complexity of the 'login' form - thanks for changing that promptly. 16:38:00 kevin: I shared the above sheet with AG. 16:38:04 jamesn has joined #waicc 16:38:16 maryjom has joined #waicc 16:38:18 kevin: TheLounge has been used for a while, but not the primary IRC platform. 16:38:24 present+ 16:38:39 ... Daniel reviewed for accessibility (issues found are in the Doc above). 16:38:46 rrsagent, make minutes 16:38:47 I have made the request to generate https://www.w3.org/2024/04/22-waicc-minutes.html jamesn 16:38:55 present- MaryJo 16:39:00 ... Daniel will file the issues with TheLounge - ideally we will get them fixed upstream. 16:39:12 ... The plan is for the Team to regularly take the latest release and adopt it. 16:39:30 ... Looking into color. There are two stylesheets being used - dark mode and not. This is within our ability to address. 16:39:38 ... Dropouts are a trickier issue. Not clear why that's happening. 16:40:09 kevin: The more info we can get about the dropouts, the better. Can pass on to sys team. 16:40:20 jamesn_ has joined #waicc 16:40:33 q+ to note that TheLounge is optional, can use client 16:41:31 kevin: Re the rollout, apologies. TheLounge has been around for a while as another option. There was rationalization of the servers involved. Sorry for the lack of notice. 16:41:38 ack me 16:41:38 shawn, you wanted to note that TheLounge is optional, can use client 16:42:05 shawn: It is optional; you can use a client on your own machine. We should still get it accessible. 16:42:19 janina: There aren't good clients that are accessible on Windows. 16:42:55 janina: We have a lot of members who just use the browser version, so important that it's workable for them. 16:43:40 q+ 16:43:44 janina: Re dropouts - is there any logging on the back end that could inform the sys team what's going on? 16:44:11 ack j 16:44:12 kevin: We need to prioritize accessibility requests (over new features). Anything that helps us fix big issues as quickly as we can would be of help. 16:44:47 jamesn: Is this a stripped-down version we're using? It looks like a product that may have features like saving channels etc. so they are there when you log in (like with IRC Cloud). Would be awesome if so. 16:45:16 kevin: This is not a stripped-down version AFAIK. It's a project available on GitHub. 16:46:19 kevin: Some Team members have a different type of connection (persistent) that may be making it harder for us to determine the cause of the problems. 16:46:45 shawn: Next steps - there are two different Google Docs - should be only one? 16:47:16 kevin: One contains everything Daniel already identified. 16:47:29 shawn: Action item to at least point to eachother, or combine them. 16:47:46 kevin: I added pointers to each. 16:47:49 zakim, next item 16:47:49 agendum 3 -- Updates around the table -- taken up [from shawn] 16:48:24 q+ to note research TF & AG work 16:48:45 q+ to mention the possibility of PDF-AAM 16:48:45 janina: We spent some time in last week's APA call in how we may be able to get pretty thorough accessibility out of fixed laouts in EPUB. Will be looking for a conversation with George et al. Paul Grenier was proposing to apply some data visualization work that's being done in a CG. 16:49:06 shawn: Will that address people who need text customization? 16:49:10 janina: Appears it might, yes. 16:49:27 shawn: I'd like to keep monitoring this. 16:49:49 janina: Will keep you updated. 16:50:40 janina: Challenge is that it's a Note (not HR). We can file issues. 16:50:53 ack me 16:50:53 shawn, you wanted to note research TF & AG work 16:51:12 present+ Daniel 16:51:28 shawn: AG is working on some research stuff - reaching out to APA RQTF for coordination on that. It's coming up! 16:51:35 ack j 16:51:35 jamesn, you wanted to mention the possibility of PDF-AAM 16:51:46 janina: They're looking for stuff to do; CTAUR is nearing completion. 16:52:16 jamesn: The PDF Association is developing PDF-AAM for PDF UA 2. Not sure where it will be done yet, but it will be great to standardize this. 16:52:26 ... They want to follow the model we have with AAMs. 16:53:18 shawn: Challenges with text customization with PDF. 16:53:26 jamesn: That is possible, could be a UA feature. 16:53:48 shawn: No UAs allow text customization though. 16:54:21 shawn: Concerned that this means it's a limitation of the technology. 16:55:14 jamesn: I don't think it's a fundamental problem of the technology. Can you not customize the text in any of the new UAs that support reflow? 16:55:59 jamesn: There are many web sites where you can't reflow the text. There is a WCAG standard but that doesn't mean it works in all cases. 16:56:41 q+ 16:56:50 shawn: I can't make it so that any UA can change the line spacing, for example. 16:57:01 ack m 16:57:14 jamesn: Can we still do work that improves things for some users? E.g. adding roles. 16:57:17 shawn: Yes 16:58:10 maryjom: There's a clause "in content that supports markup languages" - which means PDF passes, on the basis that it's not a markup language. 16:58:42 shawn: This part of the challenge - technically it meets WCAG, but it's not accessible in practice for users who need this customization. 16:59:03 maryjom: Part of the question is: Is PDF a markup language? (Relevant for WCAG2ICT) 16:59:47 shawn: Currently we have this situation where due to policy, PDF can meet WCAG but not support some areas of accessibility. 17:00:33 jamesn: We still aim to make things better at each step. 17:00:50 shawn: Agree 17:01:23 rrsagent, make minutes 17:01:24 I have made the request to generate https://www.w3.org/2024/04/22-waicc-minutes.html matatk