Meeting minutes
TheLounge <https://github.com/thelounge/thelounge/issues >
https://
janina: COGA and AG collecting issues with TheLounge in the [above] Google Doc
janina: People all over the planet are getting disconnected a lot, two or three times an hour sometimes.
janina: Not sure if anyone's filed that issue yet (need to check).
… Also there are color contrasts that don't meet WCAG.
… Are these W3C implementation issues, or are they upstream issues?
… 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.
<kevin> AGWG Issues
matatk: There was also concern about the complexity of the 'login' form - thanks for changing that promptly.
kevin: I shared the above sheet with AG.
kevin: TheLounge has been used for a while, but not the primary IRC platform.
… Daniel reviewed for accessibility (issues found are in the Doc above).
… Daniel will file the issues with TheLounge - ideally we will get them fixed upstream.
… The plan is for the Team to regularly take the latest release and adopt it.
… Looking into color. There are two stylesheets being used - dark mode and not. This is within our ability to address.
… Dropouts are a trickier issue. Not clear why that's happening.
kevin: The more info we can get about the dropouts, the better. Can pass on to sys team.
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.
<Zakim> shawn, you wanted to note that TheLounge is optional, can use client
shawn: It is optional; you can use a client on your own machine. We should still get it accessible.
janina: There aren't good clients that are accessible on Windows.
janina: We have a lot of members who just use the browser version, so important that it's workable for them.
janina: Re dropouts - is there any logging on the back end that could inform the sys team what's going on?
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.
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.
kevin: This is not a stripped-down version AFAIK. It's a project available on GitHub.
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.
shawn: Next steps - there are two different Google Docs - should be only one?
kevin: One contains everything Daniel already identified.
shawn: Action item to at least point to eachother, or combine them.
kevin: I added pointers to each.
Updates around the table
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.
shawn: Will that address people who need text customization?
janina: Appears it might, yes.
shawn: I'd like to keep monitoring this.
janina: Will keep you updated.
janina: Challenge is that it's a Note (not HR). We can file issues.
<Zakim> shawn, you wanted to note research TF & AG work
shawn: AG is working on some research stuff - reaching out to APA RQTF for coordination on that. It's coming up!
<Zakim> jamesn, you wanted to mention the possibility of PDF-AAM
janina: They're looking for stuff to do; CTAUR is nearing completion.
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.
… They want to follow the model we have with AAMs.
shawn: Challenges with text customization with PDF.
jamesn: That is possible, could be a UA feature.
shawn: No UAs allow text customization though.
shawn: Concerned that this means it's a limitation of the technology.
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?
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.
shawn: I can't make it so that any UA can change the line spacing, for example.
jamesn: Can we still do work that improves things for some users? E.g. adding roles.
shawn: Yes
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.
shawn: This part of the challenge - technically it meets WCAG, but it's not accessible in practice for users who need this customization.
maryjom: Part of the question is: Is PDF a markup language? (Relevant for WCAG2ICT)
shawn: Currently we have this situation where due to policy, PDF can meet WCAG but not support some areas of accessibility.
jamesn: We still aim to make things better at each step.
shawn: Agree