Thread Subject: Re: Latest "controls" 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: Larry Goldberg
Date: Tue, Oct 23 2007 10:00 AM


As a matter off fact, alternate language was proposed by Andrew last week
that said,

"Hardware products that receive or display analog or digital television
must provide controls needed for users to enable captioning and audio
description."

See his e-mail of Oct. 18.

The conversation continues...

... Larry ...


Sean Hayes wrote:

> OK, but we still have a problem with the term "easily", it not well defined as
> it stands.
>
> Sean Hayes
> Incubation Lab
> Accessibility Business Unit
> Microsoft
>
> Office: +44 118 909 5867,
> Mobile: +44 7875 091385
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Larry Goldberg
> Sent: 23 October 2007 16:39
> To: TEITAC AV list; Al Sonnenstrahl; = EMAIL ADDRESS REMOVED = ; Toby R. Silver;
> = EMAIL ADDRESS REMOVED = ; = EMAIL ADDRESS REMOVED =
> Subject: [teitac-video] Latest "controls" language
>
> As far as I know, we are still working with the two options offered by Dave
> Singer in our last conference call:
>
>
> In order to comply with this subpart, the user controls needed to
> configure and activate any accessibility feature, and the general
> controls used by those needing that accessibility feature, on
> products that receive or display analog or digital television, must
> be easy to find and easy to use by people needing that accessibility
> feature. In at least one location, these must be comparable in
> prominence to the controls needed to control volume, or perform
> program selection, where the ability to control these features is
> otherwise provided.
>
> * * * *
>
> And attempted re-write for clarity:
>
> In products that receive or display analog or digital television, a
> user needing access to an accessibility feature must be able to find
> easily, and use easily, both the controls needed to enable that
> accessibility feature, and other general controls that that user also
> needs to be able to use. In at least one location, these controls
> must be comparable in prominence to the controls needed to control
> volume, or perform program selection, where the ability to control
> these features is otherwise provided.
>
> * * * *
>
> The examples remain unchanged.
>
>
> For example:
> 1. For captioning:
> (a) A caption on/off on a TV remote comparable in prominence to the
> volume control on that remote;
> (b) Caption controls on the first menu that appear when on-screen
> menus are displayed
>
> 2. Audio equivalents to on-screen information and visual menu selections
> 3. A tactile button to turn on audio equivalents;
> 4. A user preferences dialog that is accessible and directly
> reachable from a login screen.
>
>
>
> - Larry
>
>
>
>


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