Hello. Please sign in!

36 CFR Part 1194 - Proposed Information and Communication Technology (ICT) Standards and Guidelines NPRM - Preamble

This document is the preamble to the NPRM. Click here to view the NPRM. See also: Final Rule published to the Federal Register 1/18/17 that jointly updates requirements for ICT covered by Section 508 of the Rehabilitation Act and Section 255 of the Communication Act.

410 ICT with Two-Way Voice Communication (Section-by-Section Analysis)

This is an introductory section.

410.1 General (Section-by-Section Analysis)

This section addresses the accessibility of telecommunications equipment that offers two-way voice communication (i.e., an interactive, multi-party voice communication occurring in real time), including both older technologies (such as landline telephones and two-way pagers) and more modern ICT (such as mobile wireless devices). It would also apply to two-way video communication when the video also transmits voice communication. Proposed 410.1 would require ICT with two-way voice communication functionality to conform to the technical requirements in proposed 410.2 through 410.8, which cover, among other things: volume gain magnetic coupling, minimization of interference, real-time text functionality, and video communication.

410.2 Volume Gain (Section-by-Section Analysis)

This section proposes to require ICT with two-way communication to provide volume gain conforming to the FCC’s current regulation at 47 CFR 68.317, which establishes technical standards for volume control on analog and digital telephones to facilitate hearing aid compatibility. The proposed section would replace existing 508 Standards § 1194.23(f) and existing 255 Guidelines § 1193.43(e). The Advisory Committee recommended that the Board adopt the FCC’s volume gain requirements for landline ICT with two-way voice communication.

In July 2013, the FCC issued a request for comment on a petition for rulemaking filed by a telecommunications industry group requesting that the agency revise its hearing aid compatibility volume control gain requirements for analog and digital telephones.10 The Telecommunications Industry Association (TIA) petition urged the Commission to issue a notice of proposed rulemaking to, among other things, update its Part 68 rule to incorporate the most recent TIA standard for hearing aid compatibility volume control on telephones: ANSI/TIA-4965, Receive Volume Control Requirements for Digital and Analog Wireline Handset Terminals (2012). 28 FCC Rcd. at 10338-39. At present, the Commission’s regulation at § 68.317 sets forth separate requirements for analog and digital telephones based on speech amplification metrics known as “Receive Objective Loudness Rating” (ROLR). ANSI/TIA-4965, on the other hand, uses a new amplification metric—referred to as “conversational gain”—to establish requirements for both analog and digital telephones.

While the “conversational gain” method of measuring amplification for wireline phones in ANSI/TIA-4965 may hold promise, it would be premature for the Board to reference this standard unless and until it is adopted by the FCC. As the lead regulatory agency on hearing aid compatibility standards for wireline telephones, the FCC is in the best position to assess the technical merits, as well as costs and benefits, of referencing this new TIA standard in any subsequent revisions to its existing regulation in Part 68.

Question 26. The Board proposes to adopt 47 CFR 68.317, which is the FCC’s current regulatory standard addressing volume control for analog and digital telephones. In the future, should the FCC revise its regulation and incorporate by reference ANSI/TIA-4965 (or any other consensus standard) for wireline phones, the Board plans to update its regulations—as needed— to reflect revisions by the Commission. We seek comment on this proposed course of action.

10 See Request for Comment on Petition for Rulemaking filed by the Telecommunications Industry Association Regarding Hearing Aid Compatibility Volume Control Requirements, 28 FCC Rcd. 10338 (July 19, 2013) (TIA Petition). The comment period on this petition closed in September 2013. Id.

410.3 Magnetic Coupling (Section-by-Section Analysis)

This section proposes to require that, where ICT with two-way voice communication delivers output by an audio transducer that is typically held up to the ear, it provide a means for effective magnetic wireless coupling to hearing technologies, such as hearing aids, cochlear implants, and assistive listening devices. This section is equivalent to §§ 1194.23(h) and 1193.43(i) of the existing 508 Standards and 255 Guidelines, respectively.

410.4 Minimize Interference (Section-by-Section Analysis)

This proposed section would require wireless handsets and digital wireless devices to reduce interference with hearing technologies to the lowest possible level, with interference specifications set forth in proposed subsections 410.4.1 (wireless handsets) and 410.4.2 (digital wireline). This section closely corresponds to existing 508 Standards § 1194.23(i) and 255 Guidelines § 1193.43(h), but also incorporates by references consensus standards developed since the 508 Standards and 255 Guidelines were published.

The proposed subsections 410.4.1 and 410.4.2 refer to industry-accepted standards for performance requirements for mobile and landline telephones.

410.4.1 Wireless Handsets (Section-by-Section Analysis)

This section proposes that ICT in the form of wireless handsets—that is, cellular telephones—would be required to conform to ANSI/IEEE C63.19-2011, as incorporated by reference in 508 Chapter 1 and 255 Chapter 1.

410.4.2 Digital Wireline (Section-by-Section Analysis)

This section proposes that ICT in the form of digital wireline devices (such as VoIP-based office desk telephones) would be required to conform to TIA 1083, as incorporated by reference in 508 Chapter 1 and 255 Chapter 1.

410.5 Digital Encoding of Speech (Section-by-Section Analysis)

This section proposes to require ICT with two-way voice communication to transmit and receive digitally encoded speech in the manner specified by ITU-T Recommendation G.722, a consensus standard for encoding and storing digital audio information that is incorporated by reference in 508 Chapter 1 and 255 Chapter 1. An exception for closed systems would exempt such systems from conformance to ITU-T Recommendation G.722 provided that they conform to another standard that ensures equivalent or better acoustic performance and support conversion to ITU-T Recommendation G.722 at their borders. This provision was recommended by the Advisory Committee to help improve auditory clarity for persons with hearing impairments. It is new to both the 508 Standards and 255 Guidelines.

410.6 Real-Time Text Functionality (Section-by-Section Analysis)

This proposed section establishes requirements for RTT functionality for ICT that provides real-time voice communication. As noted previously, both the Advisory Committee and the Board believe that RTT represents an important technological advance that provides an equivalent alternative to voice communications for persons who are deaf, as well as those with limited hearing or speech impairments. RTT delivers a more interactive, conversational communication experience compared to standard text messaging. It also provides superior speed and reliability in emergency situations. Furthermore, RTT permits the user to communicate using mainstream devices—such as mobile phones—rather than having to use specialized and expensive devices (such as TTYs). See discussion above in Section IV.E.4 (Rulemaking History – 2010 and 2011 ANPRMs: Significant Issues – Coverage of Real-Time Text), and Section V.D (Major Issues – Real-Time Text).

Proposed 410.6 would require that, where ICT supports real-time voice communication, it must also support RTT functionality. Subsections of this proposed provision would, in turn, establish technical requirements for display, text generation, and interoperability. Importantly, proposed 410.6 would not mandate that all ICT provide RTT functionality. Rather, only those ICT that already have real-time voice communication capabilities would be required to support RTT functions. In this way, the Board’s approach to requirements for RTT in the proposed rule mirrors the approach taken in the existing 508 Standards and 255 Guidelines toward TTY compatibility. Neither the existing standards and guidelines nor the proposed rule establish an across-the-board command that telecommunications equipment or devices “build in” text capability. Instead, both sets of rules simply require that, when such equipment or devices offer voice communication functions, they must also ensure compatibility with certain types of text communication (i.e., TTY and RTT) by supporting use of specified cross-manufacturer, non-proprietary signals. See 36 CFR 1193.51((e), 1194.23(b).

410.6.1 Display of Real-Time Text (Section-by-Section Analysis)

This proposed section is new to the 508 Standards and 255 Guidelines and would require that, wherever ICT provides real-time voice communication and includes a multi-line screen, the ICT must also support the display of real-time text. This provision would not apply to telecommunications devices that either do not have display screens, or only have display screens capable of showing one line of text at a time.

410.6.2 Text Generation (Section-by-Section Analysis)

This proposed section is new to the 508 Standards and 255 Guidelines and would require that, wherever ICT provides real-time voice communication and includes a keyboard, the ICT must also support the generation of real-time text.

410.6.3 Interoperability (Section-by-Section Analysis)

This section proposes that, where ICT with real-time two-way voice communication operates outside of a closed network or connects to another system, such ICT must ensure real-time text interoperability by using one of two cross-manufacturer, non-proprietary consensus standards depending on the nature of the system with which it is exchanging information—namely, a traditional telephone network or Internet-based telephony.

410.6.3.1 PSTN (Section-by-Section Analysis)

This section proposes that, where ICT with real-time two-way voice communication interoperates with the publicly switched telephone network (PSTN), real-time text conform to TIA 825-A (incorporated by reference in 508 Chapter 1 and 255 Chapter 1). This is the current industry standard for TTY signals (also known as Baudot) at the PSTN interface.

410.6.3.2 VoIP Using SIP (Section-by-Section Analysis)

This section proposes that, where ICT with real-time two-way voice communication interoperates with “Voice over Internet Protocol” (VoIP) products or systems that use Session Initiated Protocol (SIP), real-time text conform to RFC 4103 (incorporated by reference in 508 Chapter 1 and 255 Chapter 1). In Question 8 above, see Section V.D., the Board seeks comment regarding the potential benefits, costs, and drawbacks associated with referencing other standards in addition to RFC 4103.

410.6.4 Voice Mail, Auto-Attendant, and IVR Compatibility (Section-by-Section Analysis)

This section proposes that, where ICT provides real-time two-way voice communication, any associated voice mail, auto-attendant, and interactive voice response systems must be compatible with real-time text functionality. This section derives from existing 508 Standards §§ 1194.23(c)-(e), as well as existing 255 Guidelines §§ 1193.51(d)-(e).

410.6.5 HCO and VCO Support (Section-by-Section Analysis)

This section proposes that, where ICT provides real-time two-way voice communication, it must permit users to intermix speech with the use of real-time text. Such ICT would also be required to support modes that are compatible with Hearing Carry Over (HCO) and Voice Carry Over (VCO). This provision is collectively derived from existing 508 Standards § 1194.23(a) and 255 Guidelines § 1193.51(d), and is consistent with changes in technology over time from TTYs to real-time text functionality. It is particularly significant in preserving the use of HCO/VCO with evolving technology.

410.7 Caller ID (Section-by-Section Analysis)

This section proposes that, where ICT provides two-way voice communication, any associated caller identification or similar telecommunications functions must be presented in both visual (e.g., text) and auditory formats. This requirement would be new to the 255 Guidelines, but corresponds to a similar requirement in § 1194.23(e) of the existing 508 Standards. This proposed requirement could be met, for example, by having the system provide Caller ID in an auditory format, or by ensuring that Caller ID is available to assistive technology. Presentation of Caller ID in both visible and auditory forms ensures that individuals with visual impairments, hearing loss, or both, could use Caller ID and similar services, when provided.

410.8 Video Communication (Section-by-Section Analysis)

This section proposes that ICT with real-time video functionality must ensure that the quality of the video is sufficient to support communication through sign language. This proposed section would be new to both the 508 Standards and 255 Guidelines. The Advisory Committee recommended that the Board include a provision requiring ICT used to transmit video communications in real-time to meet certain specifications for video quality and fluidity (i.e., speed, data stream, and latency). See TEITAC Report, Part 6. Subpt. C, Rec. 6-E.

The Board’s proposals relating to the requisite quality of real-time video communications have received mixed reviews from commenters. In the 2010 ANPRM, the Board proposed specifications for the quality of real-time video communication that largely mirrored the Advisory Committee’s recommendation. Many commenters expressed support for the general concept of a video quality requirement as important for ensuring the accessibility of a means of communication, which, for persons who are deaf or hard of hearing, is the functional equivalent of voice communication. Some commenters, on the other hand, were critical of the Board’s proposed technical specifications as overly prescriptive or unsupported by research. In light of such concerns, in the 2011 ANPRM, the Board simply proposed—as here in this proposed rule—that the quality of video must be sufficient to support sign language communication. Commenters to the 2011 ANPRM, while again generally supportive of the effort to ensure real-time video communications were usable by persons with hearing impairments, largely took issue with the proposal’s lack of testable measures.

While the Board is mindful of commenters’ criticisms to the 2011 ANPRM’s performance-based standard for video quality of real-time video functionality, the Board has nonetheless retained this standard in this proposed rule. This provision would cover video communication via the web on dedicated videophones, as well as commonly used ICT such as smartphones. We are not aware of standards or specifications for video quality that would provide testable and achievable metrics to assess the quality and transmission of real-time video communications. However, technologies—as well as standards development—have progressed greatly in recent years. We welcome public comment on technological improvements or useful metrics relating to real-time video communication developed since the 2011 ANPRM.

Question 27. Does the performance-based standard in proposed 410.8 ensure that video quality would be sufficient to support a real-time video conversation in which one or more parties use sign language? If not, are there standards for video quality or transmission that would better implement the accessibility goal of this proposed requirement? Would it be readily achievable for manufacturers of telecommunications equipment to comply with section 410.8?

[MORE INFO...]

*You must sign in to view [MORE INFO...]