Thread Subject: Re: video support language - revised language

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: Gunnar Hellström
Date: Mon, Oct 01 2007 2:35 PM

Is it possible to also provide reference to the document that contains
explanations of the figures?

ITU-T H-Series Supplement 1. Sign language and lip-reading real-time
conversation using low bit rate video communication

http://www.itu.int/rec/T-REC-H.Sup1/en

The interested designe will then understand the relation between the
perception characteristics and features of sign language and lip reading and
how the performance figures influences usability for this application.





-------------------------------------------------------------------
Gunnar Hellström
Omnitor
= EMAIL ADDRESS REMOVED =
Tel: +46708204288
www.omnitor.se <http://www.omnitor.se/>


_____

From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
Vanderheiden
Sent: Monday, October 01, 2007 9:27 PM
To: 'TEITAC Telecommunications Subcommittee'
Subject: Re: [teitac-telecom] video support language - revised language



I think we were going to add a note:



Note: 20 frames per second or better is recommended to facilitate lip
reading and fingerspelling.




Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Karen Peltz
Strauss
Sent: Monday, October 01, 2007 2:16 PM
To: TEITAC Telecommunications Subcommittee
Subject: Re: [teitac-telecom] video support language - revised language

Here is what I think we agreed on. However, it does not include mention of
H.323.



Video Support



1. Each agency must ensure the ability of individuals to have
communication access via point to point real time video communications and
video relay services for incoming and outgoing calls.

2. Communication products or systems that are used to transmit video
communications in real time between and among individuals must support
interoperability to permit communication between and among users of
terminals from different manufacturers and service providers.

3. Communication products or systems that are used to transmit video
communications in real time between and among individuals must provide an
external flashing system that is capable of alerting users of incoming
calls.

4. At a minimum, video communications must support 15 frames per
second, QCIF resolution, and a latency of less than 400 milliseconds, in
order to provide sufficient quality and fluency that will support real time
video communication in which one or more parties are using sign language or
is talking in the picture.

5. Where security concerns are present, this subpart remains in effect,
but may be achieved by measures that prevent an individual?s video
communications from intermingling with packets of the general government
network, for example, through the installation of a separate line to an
isolated communications terminal.



Advisory note: The requirement to permit video communications in real time
includes the ability to send and receive video mail, much in the same way
that voice telephone users are able to send and receive voice mail.





__________ NOD32 2563 (20071001) Information __________

Detta meddelande dr genomsvkt av NOD32 Antivirus.
http://www.nod32.com

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University