Thread Subject: 2.2-C Audio Connection
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: Robert_Nerhood@Dell.com
Date: Mon, Oct 29 2007 8:30 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: 2.2-C Audio Connection"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
All,
Per the last TEITAC con-call, the three proposals for the Audio
Connection language are presented below. Some of the concerns voiced
include the complexity and specificity in the language as it has
evolved. The telecom, hardware, and closed subcommittee's have been
cc'd for technical comment. The TEITAC committee needs to determine the
next step relative to which version or versions to propose for the
draft.
Version 3 is the most recent proposal that should be reviewed. Due to
the complexity that has arisen around this requirement due to it's
impact on multiple products and conditions (public and private) please
review and provide comment including a vote "for" or "against" version
3.
Many thanks,
Rob
2.2-C - Audio Connection
Version 1:
When products provide auditory output beyond simple tonal feedback or
signaling, the audio signal must be provided at a standard signal level
through an industry standard connection that will allow for private
listening.
* If the product is a public-shared product then the connection
must be via a standard 2.5mm or 3.5mm audio jack.
* If the product is personal-private product then the connection
can be wired or wireless as long as a 2.5mm or 3.5mm phone jack adapter
is available from the manufacturer.
Alternate wording for clarity
* Public-shared products must provide the connection via a
standard 2.5mm or 3.5mm audio jack.
* Personal-private products may provide either a wired or wireless
connection. A wired connection must be via a standard 2.5mm or 3.5mm
audio jack. A wireless connection may be used as long as a 2.5mm or
3.5mm phone jack adapter is available from the manufacturer.
Version 2, posted to plenary email Oct 19, 2007:
When products provide auditory output beyond simple tonal feedback or
signaling, the audio signal must be provided through an industry
standard connection that will allow for private listening.
* Public-shared products must provide the connection via a
standard 2.5mm or 3.5mm phone jack or RCA audio jack.
* Personal-private products must provide either a 2.5mm or 3.5mm
phone jack or a wired or wireless connection that has a 2.5mm or 3.5mm
phone jack adapter that is commonly available.
Version 3, posted to plenary email Oct 20, 2007:
When products provide auditory output beyond simple tonal feedback or
signaling, one of the following must be true:
1. Conforming Handset: Auditory output is available via audio
transducer that is designed to be held up to the ear that meets 2.2-A
(Magnetic Coupling), 2.2-B (Interference with Hearing Device), and 2.2-E
(Volume - gain) and product does not require simultaneous use of
keyboard; or
2. Phone Jack: A standard 2.5mm or 3.5mm audio jack for
headphones/headsets is provided or
3. Any Connection with Adapter avail: Product is a not designed to
be located in a public location and an adapter from the product's audio
output format to a 2.5mm or 3.5mm phone jack is commonly available or
available from the manufacturer.
4. Public Display only: Product is designed for public audio or
audio-video display only and there is a standard audio output on the
product-system (which can be but does not need to be accessible to the
public).
* Note: RJ-9, RCA, USB, and Bluetooth connections all have
commonly available adapters. Products (not designed for public
locations) with these or other forms of audio connection that have
adapters would meet 2.2-C-(c)
* Note: Public Display systems need to meet other provisions in
the guidelines including the ability to display captions and
supplemental audio.
- Next message in Thread: Gregg Vanderheiden: "Re: 2.2-C Audio Connection"
- Previous message in Thread: None