Thread Subject: 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 11:50 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Dave Singer: "Re: Latest "controls" language"
- Previous message in thread: Greg Fields: "Re: Latest "controls" language"
- Messages sorted by: Author | Thread | Date
Here are the latest drafts which I just read out.
- Larry
------ Forwarded Message
> From: Greg Fields < = EMAIL ADDRESS REMOVED = >
> Reply-To: TEITAC Audio/Video Subcommittee < = EMAIL ADDRESS REMOVED = >
> Date: Tue, 23 Oct 2007 12:09:58 -0400
> To: TEITAC Audio/Video Subcommittee < = EMAIL ADDRESS REMOVED = >, Al
> Sonnenstrahl < = EMAIL ADDRESS REMOVED = >, < = EMAIL ADDRESS REMOVED = >, "Toby R. Silver"
> < = EMAIL ADDRESS REMOVED = >, < = EMAIL ADDRESS REMOVED = >, < = EMAIL ADDRESS REMOVED = >
> Conversation: [teitac-video] Latest "controls" language
> Subject: Re: [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.
------ End of Forwarded Message
- Next message in Thread: Dave Singer: "Re: Latest "controls" language"
- Previous message in Thread: Greg Fields: "Re: Latest "controls" language"
WebAIM is an initiative of:
