Meeting minutes
title: RQTF meeting
Accessibility of machine learning and generative AI.
jasonjgw: Any changes or discussion time?
scott_h: I put some notes in github issues. Discussion is exciting and scope being pushed and debated. Continue things on list in the coming week, given Josh can't join us today/tonight.
jasonjgw: If Josh joins we can circle back. What he was describing was largely in the scope, unless mistaken?
Janina: It is, but we landed last week that we didn't communicate some of what we thought was in scope clearly enough.
jasonjgw: the draft reviewed was prior to the scope section being added. Maybe that was clarified with scope section addition?
janina: placeholders in larger skeleton for scope/table of contents
jasonjgw: Scott- will it fit your agenda in next week or so to amend or add sections that need it?
scott_h: user perspectives and remediation perspectives, some of the higher potential issues that could be addressed. TOC and placeholder as we put things against it is a good idea. Continue the dicussion.
jasonjgw: Gives two weeks with holidays, remove time pressure?
Collaboration Tools Accessibility User Requirements.
jasonjgw: noticed Janina was active on issues list
janina: 84, 85, 86, 87, 88 left
http://
janina: If we go off to read this go to user need/requirement 20. Do we keep this or not? Other changes I can detail. Let's start with this one
jasonjgw: I'd like to review on my own time outside of the meeting
Janina: I can talk through it. Substantial changes and want your review. Generally comfortable with introduced changes (in a branch), want group mind. Done with edits tomorrow, think I'm within an hour of finishing.
jasonjgw: I can give it a day or two, or you can give a signal. Then I can go look.
janina: three weeks left to talk if we want to publish, need an APA review to finalize as a note. These are comments from last wide review, in a good process place. Nice if we could deliver this, this year. Current charter runs through July, we have time to meet our charter dates. Mindful that we're running out of time.
janina: would like to clear these out, helps APA.
Janina's recital at: https://
janina: two challenges, we said it was going to happen, now it has (captcha). We should document some of the new ways. How we wrap up with where we are with technology right now. What is the leading edge of unmediated (where user is unengaged) where that is. Not sure how to document that today, and I think that needs to be documented.
janina: Can we agree on list? Then APA can start a call for consensus. Sooner we do that, the better
jasonjgw: consensus on Janina's changes, clear of issues and call for APA consensus? Anyone dissent from that opinion?
janina: Caveat, I added user need 20 provisionally, if too far into software design, we can drop that section. Let's decide that on list.
jasonjgw: if comfortable proceeding with the changes...?
janina: I closed all of the ones I covered in the branch from 73-83
jasonjgw: once we have all of that and we're satisfied, ready to start publishing. in Two weeks when we come back, might be able to put a resolution to publish.
janina: do that in email and point to thread and start APA call for consensus (everyone here gets to vote on that). If we're going to publish before EOY we need to get this to Roy soon.
jasonjgw: final decision in 2 weeks to publish this year.
Janina: If someone has a lot of suggestions for changes in our docs, should we add them as an editor?
jasonjgw: or at least some kind of acknoweldgement?
Miscellaneous topics.
jasonjgw: publishing efforts, broadly. captcha on the list, what else?
janina: immersive captions
janina: messaging ready? if it's not ready, maybe after holidays.
janina: do we feel captcha would benefit for wide review before adding the note?
jasonjgw: new material and new techniques, wouldn't hurt to get comments on that. Wise to get that.
scottq: doesnt' hurt to put it out there and see what else needs to be added. If anything we've overlooked, good for a wide review for anyone else to chip in.
jasonjgw: noticed less captcha around in the last several years.
jasonjgw: think we're under control with publications. Anything else happening in WWW that we need to know about?
jasonjgw: podcast Microsoft released a new website that uses a large language model and web searches of their own site to answer questions about a11y in their products.
janina: we should cover that in our document
jasonjgw: does produce references with its answers so you can go read more. More than a serach engine, it's answering the question not just finding the references.
janina: can it give markup?
jasonjgw: doubt it. It's in their documents. How to turn on captions in microsoft teams would have a good chance of answering.
jasonjgw: I think we're going to see more of this. Econmic lure of an autmatic tech support machine for corporations is sensitive about costs, even if not largely accurate. Put disclaimers on it and start using it, some might create these and put them in as first line of technical support.
Jason: we need to acknowledge it's going to raise skill requirements for entry-level support people, answering questions that aren't just in a script. Risk - a11y info might not be included, and output might not explain the task in an accessible manner. Issue there as well. Probably need to say something about this in documentation.
jasonjgw: the number is going to grow.