W3C home > Mailing lists > Public > public-rqtf@w3.org > July 2019

Re: Action-2201 Blind users texting interfaces

From: Joshue O Connor <joconnor@w3.org>
Date: Tue, 9 Jul 2019 09:56:03 +0100
To: Janina Sajka <janina@rednote.net>
Cc: public-rqtf@w3.org
Message-ID: <ffea6f80-0f1b-6dc1-cc2b-5aca47f38466@w3.org>
Great! Thanks Janina - will review/comment and add to our Accessible RTC 
doc.

Josh

On 08/07/2019 23:44, Janina Sajka wrote:
> Follows a draft use cast statement covering text-based conversation
> interfaces at variance with RTT.
>
> ***cut here***
>
> The traditional IRC interface must be preserved at least as a
> configuration option in agents that implement WebRTC. Users who rely on
> text to speech (TTS) to interface with their computers and smart devices
> require the IRC style interface as opposed to the RTT type interface
> favored by users who are deaf or hearing impaired.
>
> The use case for RTT is important and should certainly be supported by
> WebRTC. This use case does not compete with the use case for RTT. Both
> should be supportable in the text stream provided by WebRTC. We
> understand why users who can comprehend chars in real time, as they're
> typed by a remote correspondant in a telecommunications session, are
> important to text interface users using display screen technology. Users
> should be supported in seeing those chars with very minimal latency.
>
> Arguably, some braille users will also prefer the RTT model. However,
> braille users desiring text displayed with standard contracted braille
> might better be served in the manner users relying on TTS engines are
> served, by buffering the data to be transmitted until an end of line
> char is reached.
>
> TTS cannot reasonably translate text into comprehensible speech unless
> the chars to be pronounced are transmitted in close timing to one
> another. Typical gaps will result in stuttering and highly
> unintelligible utterances from the TTS engine.
>
> NOTE: People familiar with Unix, and now Linux command line interfaces
> will understand the distinction described here as that between the two
> :s/former/latter/
> applications "write" and "talk." The former functions like RTT
> specifies. The former functions like a classic IRC session. Both need to
> be supported by WebRTC user agents.
>
> Here are links that further describe the functionality of these two
> classic Unix utilities:
>
> talk<https://www.mankier.com/1p/talk>
>
> write<https://www.mankier.com/1p/write>
>
-- 
Emerging Web Technology Specialist/A11y (WAI/W3C)
Received on Tuesday, 9 July 2019 08:54:57 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:46 UTC