12:10:29 RRSAgent has joined #rqtf 12:10:33 logging to https://www.w3.org/2026/08/12-rqtf-irc 12:10:33 RRSAgent, make logs Public 12:10:34 please title this meeting ("meeting: ..."), jasonjgw 12:10:41 meeting: RQTF meeting 12:10:46 chair: jasonjgw 12:10:48 present+ 12:10:50 scribe+ 12:10:51 agenda+ Accessibility of Machine Learning and Generative AI draft. 12:10:51 agenda+ Metaverse Standards Forum XR Accessibility Guidelines. 12:10:53 agenda+ Game accessibility. 12:10:56 agenda+ Miscellaneous topics. 12:50:00 jasonjgw has joined #rqtf 12:50:12 regrets+ josh 12:52:21 jasonjgw has joined #rqtf 13:00:01 stacey has joined #rqtf 13:00:43 JPaton has joined #rqtf 13:00:51 present+ 13:00:54 scribe+ 13:01:01 present+ John_Paton 13:03:29 janina has joined #rqtf 13:05:45 zakim, next item 13:05:45 agendum 1 -- Accessibility of Machine Learning and Generative AI draft. -- taken up [from jasonjgw] 13:07:33 Jason: Janina circulated a doc with proposed TOC and under each section there's a series of descriptive paragraphs that introduce what the issue is. Developed with aid of LLM. Thanks to Josh, Stacey, and Scott for sending comments to the group. Janina - first question - given comments so far it's broadly supported with detailed suggestions. 13:07:33 Thoughts on your side? 13:09:36 Janina: I was waiting for this meeting and not looking. Will do so now that there are comments to respond to. Bottom line - is this a path forward in a useful direction? And text in each area, worth keeping, reflects what we said and all needs tweaking and too long. But if general concensus is it's step forward then I'll proceed and incirporate 13:09:36 what we had so far in place. Caveat - I'll come back to that. So one doc in Git in our usual structure and start trimming discussion in how we got to this. Leave short paragraph of what we want to say in doc development. Caveat - we have a section on overlays. I don't think it belongs. Scripted responses, not usually AI. 13:09:54 Jason: Can make it clear it's an AT or app on website, and probably enough of what to say 13:11:20 Janina: AI can be applied anywhere in the process and analysis of the doc...helpful in understanding where things happen in the process when someone puts content online and a user with a disability needs to interact with it. But that's done after the fact in a user agent, publishing...series of places where you want a11y concerns addressed. They 13:11:20 can be addressed well or poorly. Ways to address appropriately. Original overlay was a bad outcome and that's (the fact sheet) I think it doesn't belong and can get in our way to reasonably discuss things. 13:11:46 Jason: issue that doesn't touch on ML technologies too much except can be a mechanism, trajectory from creation to usage. I think I'd agree with you 13:11:53 Janina: All dynamic. AI makes it more so 13:12:38 Jason: UI elements that are AI generated. Totally a different scenario. What you proposed TOC I think captures many more issues we've discussed than existed structure and better starting point than what we had. And use as starting point. 13:12:50 ...any objections? [no] 13:13:01 Janina: so they are perfecting comments not on the approach? 13:13:05 Jason: yes 13:14:45 ...actions to suggest: first is to take into account comments that have been made on mailing list. Detail level. Then second, further refinement and I can comment on any stage along the way. I think my comments would be at a detailed level anyway. Sections/organization. So no comments that would hold up the work. If you're satisfied that you know 13:14:45 what you're doing and we're supporting you I think it takes care of this one 13:14:57 Janina: I can progress and move forward reasonably well 13:15:17 Jason: any final questions or comments before we revisit? Maybe next week. Might be more as the work goes on. 13:15:28 Janina: Next step is to create git file and get us a branch 13:15:40 Jason: and opportunity to comment on that. I can do comments at that stage. 13:15:57 Janina: branch or retire current doc into an earlier draft? Branch still makes sense 13:16:08 Jason: makes sense. Merge would mostly replace what was there 13:16:13 janina: yes 13:16:30 Janina: OK, will think in terms of a branch 13:16:42 [no final comments and questions] 13:16:46 zakim, next item 13:16:46 agendum 2 -- Metaverse Standards Forum XR Accessibility Guidelines. -- taken up [from jasonjgw] 13:18:49 Jason: background, received request from metaverse standard forums on XR guidelines. Suspect this will be a coordination exercise. Possibly APA and A11y guidelines working group and probably treat as such. Dylan Fox...Looking for a pathway to having this influence some normative document and if going to be normative outcome then i assume a11y 13:18:49 guidelines working group. not really this task force or APA. 13:19:44 Janina: consumptin side, what constitutes a11y and web content that's their role. But that's as far as they go., If w3c writes normative guidance we want to influence that. Agree we can have that conversation if anything on that horizon. XR was a hotter topic 4-5 years ao than now. But could come back with AI. 13:20:37 Jason: question, consider metaverse standards doc, they've done a gap analysis on what they think is missing in a11y fguidelines draft and next version that they'd want to see filled in. One step that could be taken. Another step could be a w3c submission process. Need a working group? 13:22:25 Janina: could be a submission process and probably is. They could submit as is and publish as a statement (not capital S) - we want the world to know this stuff. Everyone wants a working group note. I don't know if they want to pursue that or if we want to. AI, gaming. This would be no higher than third. But, they've worked it up, Not going to say 13:22:25 no. But need to negotiate the when and the how. But there is a place you can publish a working group note of a w3c member. 13:22:31 Jason: not something that's widely cited 13:22:58 Janina: right, no consensus and someone wanting to get opinions note 13:26:39 Jason: personal view, probably a manageable number of additions to a web content a11y guideines that cover gaps made conspicuous by XR technologies. Some point in process can be added in. But needs someone to work out what they are and reduce to what the principles that should be added to the standards. And docs would be written accordingly. Right 13:26:39 way to make anythign normative as far as w3c concerned. Fair amount of work to do it. Some kind of gap analysis with accessibility guidelines. Could be wrong, but that's what seems to be. Just another web content and in accessiblity guidelines purview. 13:27:44 John: lots of people on the list who weren't regularly at meetings. Lots of people from Google. Not just Dylan. 13:28:06 Janina: i'll take it up with APA and send Dylan a note to ask what he wants to achieve inside w3c. 13:28:45 Jason: Sounds like the way to proceed. 13:29:02 Janina: if we continue the relationship, APA would kick it back here. I think we know where this would fit in our priorities. 13:29:27 Jason: Janina, let us know from the APA side 13:30:30 ...any final questions on this? 13:30:34 zakim, next item 13:30:34 agendum 3 -- Game accessibility. -- taken up [from jasonjgw] 13:31:05 Jason: i know this is ongoing topic and development. One comment to add from last week. But first John - anythign to raise to the group? 13:32:16 John: still adding to gap analysis. want to get there sooner rather than later, but competing work priorities. Discussion emails if better to have accessibility features that break the challenge of the game but still allow them in or better to say if a feature that breaks the game it should be in? That's doing the work - getting ahead of yourself. 13:32:16 I think taht's interesting but not for discussion yet 13:32:30 janina: we'll work on that and discuss when we get to the paper. 13:34:13 Jason: one of the capabilities in educational domain, might be relevant here, is that there's...the more sophisticated education systems is adaptive. large database of questions it can ask you. based on response to the first several questions can determine which questions to ask. Dynamic measuer difficulty by your responses. Games might be able to 13:34:13 operate similarly in principle. Can set level of difficulty....not sure if there are games taht already build this in? 13:34:41 Janina: isn't that doing the work? That's a gap worthy of discussion? But not the proposal to doing the work? Goes on bucket list of things to talk about 13:35:12 Jason: yes. We're always interested in accessible systems that adapt to needs of the users. Adaptations that touch on dsireable and undesireable issues. 13:36:23 John: what is intended use of the document? I want to use outcomes of this as a way to get towards regulation, a reasonableness clause in legislations/regulation. Reasonableness argument rather than saying we ought use this doc on how to make any game accessible. Could have different sections in the doc. Temptin to do the work before we have the 13:36:23 permission. 13:37:07 janina: perfectly happy to make hints to regulators. How society on how to reasonably consider how to make decisions and what to expect. What can be done technologically and governance and regulations. And outside the scope of the document. But someone needs to do it 13:37:44 Jason: Most able to achieve in writing about these design questions is giving people concepts and examples and suggestions to help them think about issues more clearly when making decisions. No clear and hard lines. These are ways of thinking about it that we think are useful. 13:38:44 Janina: Judy Brewer was really good at this. Making our pubs had this without saying we're writing this for regulators. 13:39:14 Jason: agree. A clear statement of relevant considersations are and how to approach with creativity and understanding is themost we can expect. 13:39:42 Janina: we can expect judy's help on this when direction is clear and aspect...we can ask her to take a read. She will give us her thoughts. 13:41:15 Jason: getting gap analysis abstract will get us to next stage with APA. Circle back and get into substance and what we want to say in how we make these challenging design decisions. 13:42:14 zakim, next item 13:42:14 agendum 4 -- Miscellaneous topics. -- taken up [from jasonjgw] 13:42:27 Jason: anything else going on? 13:42:56 Janina: Scott is no longer able to attend Zoom meetings regularly. 13:43:33 ...I'd like to leave the door open. I think we welcome his asynchronous work. Very much in keeping with w3c ethos. 13:49:29 Jason: going to be in Australia, So will be in that eastern time for a while. Challenging time zone. Tentatively looking at OCtober and first couple of weeks of November. Still being worked out. 13:49:41 Janina: if we need coverage, I might take that up 13:50:16 Jason: if we can find someone to co-facilitate that would be good to take that aspect up from Scott. 13:53:00 Janina: I'm traveling this weekend but will still be involved. Editing ability constrained by the technology I can bring with me. 13:56:24 zakim, end meeting 13:56:24 As of this point the attendees have been jasonjgw, stacey, John_Paton 13:56:25 RRSAgent, please draft minutes 13:56:27 I have made the request to generate https://www.w3.org/2026/08/12-rqtf-minutes.html Zakim 13:56:34 I am happy to have been of service, jasonjgw; please remember to excuse RRSAgent. Goodbye 13:56:34 Zakim has left #rqtf 13:56:34 janina has left #rqtf