Thread Subject: Re: Proposed language for user controls on video programming products

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: Karen Peltz Strauss
Date: Thu, Oct 11 2007 1:10 PM

In theory I don't have a problem with how you have revised this. I am a
little concerned about its readability though.

I will be leaving to go out of town for a while and not have much access to
e-mail again until Sunday. I will check back then to read this discussion
strand.

Karen

----- Original Message -----
From: "Dave Singer" < = EMAIL ADDRESS REMOVED = >
To: "Karen Peltz Strauss" < = EMAIL ADDRESS REMOVED = >; "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 = >
Cc: "Rosaline Crawford" < = EMAIL ADDRESS REMOVED = >; < = EMAIL ADDRESS REMOVED = >
Sent: Thursday, October 11, 2007 2:37 PM
Subject: Re: Proposed language for user controls on video programming
products


> Ooops, I missed Karen's later message and I should have started with that,
> ahem. Sorry, Karen.
>
> I get the "general and" part here is saying that people with an
> accessibility need will need two kinds of control ability (a) the need to
> control the accessibility feature and (b) the need to control everything
> else that is part of normal access.
>
>
> How about this:
>
> 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. These must be
> comparable in prominence to the controls needed to change volume and
> channels, where the ability to control these features is otherwise
> provided.
>
>
>
> 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.
>
>
>
>
> At 7:29 -0400 11/10/07, Karen Peltz Strauss wrote:
>>Here is another attempt at proposed language for user controls on video
>>programming products. I have taken a little bit from Dave's, Sean's and
>>Gregg's proposals, and here is what I have come up with. By way of
>>explanation: First, this really should stay in the audio-video section of
>>the guidelines, not a general section where it is likely to be overlooked.
>>We are talking about very specific types of controls for accessing
>>television and television-like products and it would be better if we dealt
>>with this here. Second, this provision does not belong in 1.2-A because
>>that section deals with activation by the agency - such as when
>>accessibility is built into a phone system and the agency does not trigger
>>the switch to turn on the access features built in (this was discussed at
>>length in the telecom subcommittee where this provision originated).
>>Third, I agree with Gregg that the examples may get lost, but if we
>>include some language about comparable prominence to volume and channel
>>controls, I think that will help. I know there were some concerns about
>>this, and that is why I added "where the ability to control these features
>>is otherwise provided." Finally, I tried to put this whole requirement
>>into plain English - "make the controls easy to find and easy to use":
>>
>>
>>
>>In order to comply with this subpart, the user controls needed to
>>configure and activate general and accessibility features on products that
>>receive or display analog or digital television must be easy to find and
>>easy to use by people with disabilities. These must be comparable in
>>prominence to the controls needed to change volume and channels, where the
>>ability to control these features is otherwise provided.
>>
>>
>>
>>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.
>>
>>
>>
>>Karen
>
>
> --
> David Singer
> Apple/QuickTime

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