RE: RAUR: New use case for total conversation clarification

Thank you, Josh - this is definitely evolving in the right direction. I doubt the ITU would be defining and recommending this capability if it weren't significantly desired by users with disabilities.

Am I correct in concluding that, as soon as real-time text is standardized for WebRTC sessions, all of the elements should be in place for supporting Total Conversation services? Obviously, we already have WebRTC-based voice and video sessions, with RTT being the only missing component.

-----Original Message-----
From: Joshue O Connor <joconnor@w3.org>
Sent: Thursday, October 8, 2020 9:41 AM
To: White, Jason J <jjwhite@ets.org>; RQTF <public-rqtf@w3.org>
Subject: Re: RAUR: New use case for total conversation clarification

That's really useful Jason.

> For example, one advantage is that the participants can make use of all three communication modes without having to restart the RTC session and can freely mix voice/video/RTT as desired.

Do we when want to suggest that this should be supported in toto? If so I could articulate the user need and related requirement as follows:

Draft User Need x: Total Conversation support

User Need: A person with a disability needs to use a combination of voice, video, and real-time text (RTT) in the same real-time session.

Req 1: Support the use of combined voice, video, and real-time text
(RTT) in the same real-time session.

Req 2: Ensure interoperability of voice, video, and real-time text (RTT) in the same real-time session.

Is that going in the right direction?

Feedback welcome, thanks

Josh

--
Emerging Web Technology Specialist/Accessibility (WAI/W3C)


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Thursday, 8 October 2020 13:45:42 UTC