13:36:57 RRSAgent has joined #rqtf 13:37:02 logging to https://www.w3.org/2024/02/07-rqtf-irc 13:37:02 inviting RRSAgent 13:37:02 RRSAgent, make logs Public 13:37:03 please title this meeting ("meeting: ..."), jasonjgw 13:37:24 meeting: RQTF meeting 13:37:30 chiar: jasonjgw 13:37:32 present+ 13:37:34 scribe+ 13:37:36 agenda+ Collaboration Tools Accessibility User Requirements. 13:37:36 agenda+ Miscellaneous updates and topics. 13:54:30 janina has joined #rqtf 14:02:40 DavidSwallow has joined #rqtf 14:02:53 present+ 14:05:27 zakim, next item 14:05:27 agendum 1 -- Collaboration Tools Accessibility User Requirements. -- taken up [from jasonjgw] 14:05:46 present+ 14:05:59 scribe+ 14:07:33 janina: Conveyed sense of leadership, including COGA, APA, and AG, that our process is actually working. 14:08:04 . Further, COGA will be invited to participate on a forthcoming RQTF call to review our scope creep issue decisions. 14:11:31 Janina notes the invitation for COGA participants to join an RQTF meeting. 14:13:47 subtopic: Issue 24 14:16:42 Janina: isn't sure about changing the title to "collaboration functionality", but better definitions make sense. 14:17:40 Janina: agrees it is valuable to emphasize the positive potential to enable people with various accessibility requirements to contribute collaboratively. Janina will take this on advisement. 14:19:20 jasonjgw: Notes RTC already addressed in it's on APA Note 14:20:32 Janina will re-read the document to ensure asynchronous content collaboration is properly addressed. 14:21:03 Janina will propose revisions, as needed. 14:22:57 Janina notes there's an inherent lag-time - latency in communication, even though we would still regard it as real-time. We should acknowledge the need to support inherent latency. 14:23:46 Janina: managing rapidly changing content raises issues (e.g., having different collaborators changing discrete parts of a document/content). 14:24:24 raja: ASL could be considered a collaboration support technology 14:24:43 janina: Yes, and it comes with inherent latency which is important to acknowledge 14:25:05 jasonjgw: Notes we've discussed the importance of social aspects, giving enough time for people to comprehend and implement 14:26:11 jasonjgw: We do want to elevate how we can talk positvely about collaborative success 14:26:36 jasonjgw: So, we're essentially accepting this comment even if we don't rename to CFAUR 14:27:43 Janina suggests we characterize it in terms of tools primarily, rather than functionality, as we're trying to influence the software development of environments. We have requirements for this, and we enable the developer community to implement them. 14:28:11 Janina: we acknowledge functionality, especially in referring to the social aspect as not being subsumed by tooling. 14:29:24 subtopic: Issue 25 14:30:57 janina: It's in there 14:31:20 jasonjgw: Should probably move from Intro to a numbered item, can do 14:31:55 raja: Sometimes captions can look differently in different apps; would be good if we could standardize that some 14:32:42 raja: Spotlighting an individual contributor via standard approaches might be important 14:32:58 jasonjgw: Think I could propose something like this 14:35:28 jasonjgw: Summarizes that we believe we've dealt with this issue, but we will review and see whether we can further elaborate this important point 14:38:09 subtopic: Issue 26 14:39:41 janina: Believe we've addressed, but phps could say more 14:40:43 Janina: acknowledges the need to make clear where a comment ends (in the user interface). Example: HTML