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