Thread Subject: Re: SubpartADefinitions-TTY-Action Needed
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Owen Rachal
Date: Tue, May 01 2007 8:35 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
I have to disagree here. TTYs have not expanded very much - in fact, they do not really work well over VoIP or Internet Telephony, and a computer-based TTY is no different from any other, except harder to transport, much like a soft-phone does not importantly differ from a telephone, with respect to 508. In fact, the only difference I see is that the soft TTY should follow software accessibility guidelines, as well. Also, with regard to cellular networks, I believe that TTY tones are passed pretty much the same way they are over the PSTN - using Baudot. Contrast this with IP text: no tones and no external physical device (at least, not necessarily and not yet, except perhaps IP Captel, if we want to include it), and incapable of transmitting intelligible text over the PSTN without being re-encoded.
While I understand the the literal definition of TTY easily transfers to IP, I think that we are wildly outpacing popular usage. Because TTY is synonymous with TDD in popular usage, and yet IP text is not, if we insist on equating TTY with IP text, we will not be accurately reflecting the public's perspective. While that may not be very important in some ways, if these regulations are not accessible to everyone - in this case, people who do not know that we are equating TTY with IP text, despite prevailing opinion - then they may not be enforced as intended, and people will choose to apply provisions regarding the more common understanding of TTY and may ignore their application to IP text.
NXI is a perfect example of this: I have never heard anyone refer to Nextalk as a TTY, even though it receives, decode and encodes Baudot, connects to the PSTN, transports real-time text, runs as software on both local and server machines, and is primarily intended for communicating with deaf people. I've never seen a beter marriage of IP, real-time text, and Buadot on the commercial market.
I think if we call a PC running Nextalk a TTY, then we have left the mainstream path, and people will not be able to sympathize with our intention. Better, I believe, to differentiate the two, and avoid confusion or ineffectiveness. This is also in keeping with the use of the term "terminal device" to protect the unique identity of PCs running telecommunications software (for example), as opposed to telephones or TTYs or videophones, which traditionally only perform one function. In fact, I am tempted to suggest that we drop TTY altogether and use the term Real-Time Text-Based Terminal Device, and then subdivide into TTY and IP text terminal devices. At least the difference would be analogous to that of voice communications devices, and would include TTYs, IP text, soft TTYs and Captel-style devices.
Owen Rachal,
Tenacity, Inc.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED = on behalf of Jessica M. Brodey
Sent: Tue 05/01/2007 08:37 PM
To: 'TEITAC Subpart A Subcommittee'; = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-telecom] [teitac-subparta] Subpart ADefinitions-TTY-Action Needed
I understand the desire to separate the definitions, but we do need to
recognize that TTYs have expanded from their once traditional and narrowly
defined usage, and are no longer limited to the PSTN. As such, it is
important that our definition reflect the current scope of TTYs. This
should include VoIP, Internet Telephony, cellular networks, and
computer-based TTYs. I believe this is why the new definition was drafted
in the first place.
Jessica Brodey
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
Vanderheiden
Sent: Tuesday, May 01, 2007 7:24 PM
To: 'TEITAC Subpart A Subcommittee'; = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-subparta] Subpart A Definitions-TTY-Action Needed
I think we need to separate TTY (which was defined for PSTN) with general
real-time text communication.
Suggest
TTY Machinery or equipment that employs interactive text based
communications through the transmission of coded signals across the public
switched telephone network in compliance with TIA-825-A, A Frequency Shift
Keyed Modem For Use On The Public Switched Telephone Network;
Real-time text. Text which is transmitted within 1 second of entry
providing a smooth flow of conversational text that can be mixed with
speech.
(TIA-1001 is a standard for intra-trunk communication which is a carrier
only concern. The US government wouldn't be operating telephone trunks. )
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Schomburg,
Paul
Sent: Tuesday, May 01, 2007 8:11 AM
To: TEITAC Subpart A Subcommittee; = EMAIL ADDRESS REMOVED =
Cc: Schomburg, Paul
Subject: Re: [teitac-subparta] Subpart A Definitions-TTY-Action Needed
Folks: This may be too broad a definition and might include non-standard
proprietary coding or really any text messaging (IM) service one could
imagine. I think it should be more narrowly defined as follows:
An abbreviation for teletypewriter. Machinery or equipment that employs
interactive text based communications through the transmission of coded
signals across the public switched telephone network in compliance with
TIA-825-A, A Frequency Shift Keyed Modem For Use On The Public Switched
Telephone Network; or across an IP network in compliance with TIA-1001,
Transport of TIA-825-A Signals over IP Networks.
Thanks, Paul
- Next message in Thread: None
- Previous message in Thread: None