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

Action-2201 Blind users texting interfaces

From: Janina Sajka <janina@rednote.net>
Date: Mon, 8 Jul 2019 18:44:04 -0400
To: Joshue O Connor <joconnor@w3.org>
Cc: public-rqtf@w3.org
Message-ID: <20190708224404.GK1818@rednote.net>
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>

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Monday, 8 July 2019 22:44:27 UTC

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