Thread Subject: FW: Latest controls access language (3:55pm ET)
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: Wed, Oct 17 2007 2:05 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
- Larry
------ Forwarded Message
> From: Dave Singer < = EMAIL ADDRESS REMOVED = >
> Date: Wed, 17 Oct 2007 12:57:07 -0700
> To: Larry Goldberg < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [teitac-video] Latest controls access language (3:55pm ET)
>
> sent just to Larry:
>
>
> OK, we seem to be converging. We return to volume control instead of
> mute, and it sounds as though we'll leave it specific for the moment
> to TV.
>
> We could maybe do with better text than 'easy to find and easy to
> use' (or its re-write).
>
> * * * *
>
> 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.
>
>
>
> --
> David Singer
> Apple/QuickTime
------ End of Forwarded Message
- Next message in Thread: None
- Previous message in Thread: None