13:17:38 RRSAgent has joined #rqtf 13:17:42 logging to https://www.w3.org/2023/11/29-rqtf-irc 13:17:42 RRSAgent, make logs Public 13:17:43 please title this meeting ("meeting: ..."), jasonjgw 13:18:10 meeting: RQTF meeting 13:18:20 chair: jasonjgw 13:18:24 present+ 13:18:27 scribe+ 13:19:23 agenda+ Collaboration Tools Accessibility User Requirements. 13:19:23 agenda+ Media Accessibility User Requirements. 13:19:23 agenda+ Accessibility of CAPTCHA. 13:19:23 agenda+ Miscellaneous topics. 13:51:35 janina has joined #rqtf 14:01:14 janina has changed the topic to: RQTF Teleconference 14:01:50 scott_h has joined #rqtf 14:03:19 present+ 14:03:19 scribe+ 14:03:19 present+ 14:03:19 zakim, next item 14:03:19 agendum 1 -- Collaboration Tools Accessibility User Requirements. -- taken up [from jasonjgw] 14:03:56 jason: David Swallow updating issues on GitHub 14:04:10 kirkwood has joined #rqtf 14:04:13 DavidSwallow has joined #rqtf 14:05:13 janina: walkthrough now? 14:05:30 jasON; good to work out which ones take time, which ones quick 14:06:12 david: COTGA now waiting for our feedback 14:06:25 some need clarification 14:09:09 david: COGA's issues with GitHub: 14:09:20 complexity, jargon, too many notifcaiotns, subject lines not being clear 14:10:14 janina: helpful to separate git form github to understand issues 14:11:03 jason: some ready to make decisons? 14:11:37 daivd: issue 59 14:12:03 new user need and requirement, placement unusual 14:13:18 user need: interface needs to be clear and easy to understand 14:13:32 inteface needs tob e familiar 14:13:57 requriement: help users understand what things are and use things similar to common design pattersn 14:14:33 jason: not specific to issues in the doucment, 14:15:30 not clear in context of document could we frame a requriements to follow conventions, or are range of applicaiotns oto diverse? 14:16:28 janina: concepts are in the doucment, just not specific design pattern terminolgoy 14:16:55 jason: and if places to flesh out, could be done 14:18:20 raja: seems a bit general, how is it applied generally throughout the documents? 14:18:41 janina: issue is that all softwre, whether web based on app, needs a new interface and this is problematic 14:18:57 so common patters are a benefit 14:19:41 point is made hat different types of apps have different interfaces 14:20:59 jason: in collaborative, some features concistent but interfaces may ned to be different 14:21:47 action - janina to flesh out, jason to support 14:22:35 david: lisa requested separate seciton 14:23:35 janina: further explanaiton good, not needing separate section 14:23:52 content usable - what and hwere woudl be useful 14:24:30 jason: commen may also be pointng to older draft 14:25:43 issue 58: clarify WYSIWYG 14:26:14 david: text references WYSIWYG, suggest graphica text interface 14:26:28 janina: sugget reject, WSIWYG common term 14:28:21 scott: the acronymn is defined 14:28:21 raja: does current generation understand? 14:28:21 jason: mark as no change 14:28:52 janina: using old term better than creaitng new one 14:29:08 action - janina to comment and cloe, no change 14:30:35 issue 57: 14:31:57 and 56 14:32:13 issue 56: update specificaiton with new technologies 14:32:43 quesiotn is do we need ot specifically naem all the colaborative tools in Microsoft, google etc 14:33:20 janina; hesitant to name specific products 14:34:08 raja: can we proivde best of both words - miro and google meet. miro is interactive whiteboad 14:35:06 miro dos't have captions, google met does 14:35:29 and can let peple know you can combine different tools 14:36:24 jason: RTC is not in the scope of htis document as alrady in the RAUR 14:36:46 may not meniton that specifically though 14:37:14 janina: whiteboard may need to be included though 14:37:54 RajaKushalnagar has joined #rqtf 14:38:38 should get a meniton and exmaple 14:40:19 scott: references to microsoft and google tools is already there which is good but covered enough, 14:40:30 but agree whiteboard good t cover 14:41:10 janina: yes add more on whiteboarding 14:42:24 janina: separately, need ot have a seciton to make sure everyone is included when decisions are bien gmade, eveyrone included 14:42:39 comments on sociology - not just a tehcnical porblem 14:43:47 jason: exmaple when too many notificaiotns are ocming in 14:44:27 help documentaiton and support 14:45:04 raja: when people work together, breakouts, challenge as a Deaf person with delays need to be addressed, but how to comibne tools together ot make the experience accessible is impotant 14:47:51 issue 45 asked to clarify on what is an isn't out of scope, but no more detail 14:48:49 action - issue 56, add whiteboard info as collaboration aspect 14:51:29 action - issue 57, focused on desig patterns aand accessibility e..g word processor, do not need to reference list of products - tools of all types can take what they need form the docuent, brief exmaples already included. Review to be done to check this is explained adequately 14:53:22 zakim, next item 14:53:22 agendum 2 -- Media Accessibility User Requirements. -- taken up [from jasonjgw] 14:54:16 janina: limited time to progress 14:56:18 zakim, next item 14:56:18 agendum 3 -- Accessibility of CAPTCHA. -- taken up [from jasonjgw] 14:56:51 jason: with APA, talking to security community in W3C 14:58:45 bring back in two weeks 14:59:33 zakim, next item 14:59:33 agendum 4 -- Miscellaneous topics. -- taken up [from jasonjgw] 15:00:35 zakim, end meeting 15:00:35 As of this point the attendees have been jasonjgw, scott_h, janina 15:00:36 RRSAgent, please draft minutes 15:00:38 I have made the request to generate https://www.w3.org/2023/11/29-rqtf-minutes.html Zakim 15:00:45 I am happy to have been of service, jasonjgw; please remember to excuse RRSAgent. Goodbye 15:00:45 Zakim has left #rqtf 15:02:25 janina has left #rqtf 15:03:40 kirkwood has joined #rqtf 17:21:52 kirkwood has joined #rqtf 18:24:57 kirkwood has joined #rqtf 19:44:29 kirkwood has joined #rqtf 20:59:08 kirkwood has joined #rqtf 21:37:41 kirkwood has joined #rqtf