Thread Subject: Re: A modest proposal

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, Sep 19 2007 12:35 PM

But practically, do you think anyone checking the new regs regarding media
accessibility would ever run across the text sizing reqs from another
section?

... Larry ...


Greg Fields wrote:

> The other references to platform elsewhere in the provisions don't point
> back to the specific provision as it has already been defined, outlined
> and its requirements stipulated.
>
> GregF
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman,
> Allen
> Sent: Wednesday, September 19, 2007 1:56 PM
> To: TEITAC Audio/Video Subcommittee
> Subject: Re: [teitac-video] A modest proposal
>
> That has been done previously in self-contained.
> If items in 3 cover all our needs, why not?
> a/v should focus on only the unique requirements beyond those already in
> 3--or providing changes that are critical for media playback for 3.
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Larry
> Goldberg
> Sent: Wednesday, September 19, 2007 1:52 PM
> To: TEITAC AV list
> Subject: Re: [teitac-video] A modest proposal
>
> Greg,
> Are you suggesting that all we would need to do is point to those
> provisions and indicate that software used for playing multimedia must
> comply with those regs?
>
> ... Larry ...
>
>
> Greg Fields wrote:
>
>> - Technical provision 3-D User Preferences adopts a paradigm of
>> platform settings that are global to a platform, applied across
>> multiple applications and are user-definable.
>>
>> - Provision 1.2-I already defines the requirements for text sizes
>>
>> The idea behind the proposed change to 4-A.3 is to leverage the
>> paradigm of settings available to the platform, which includes the
>> font size requirements already defined elsewhere.
>>
>> GregF
>>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Larry
>> Goldberg
>> Sent: Wednesday, September 19, 2007 12:02 PM
>> To: TEITAC Audio/Video Subcommittee
>> Subject: Re: [teitac-video] A modest proposal
>>
>> That's pretty much the issue - who is the burden put on? User,uthor/
>> producer,or manufacturer?
>>
>>
>> - Larry
>>
>> Sent from my iPhone
>>
>> On Sep 19, 2007, at 11:48 AM, Karen Peltz Strauss
>> < = EMAIL ADDRESS REMOVED =
>>> wrote:
>>
>>> How easy will it be for users to delve into the device itself to
>>> change the text size? Would there be a way to enable users to
>>> exercise control over this feature through the interface controlling
>>> the video application itself?
>>> The concern is that if a person has to leave the application that is
>>> transmitting the video and go elsewhere into the inner workings of
>>> the device, they may have a very difficult time trying to figure out
>>> how to re-size the font. This would be especially true if they are
>>> federal employees who are not familiar with the general methods used
>>> for displaying and labeling text sizes on the media equipment - for
>>> example, the situation where a person is to watch a video for a
>>> government course and is handed a media device for this purpose.
>>>
>>> Karen
>>>
>>> ----- Original Message -----
>>> From: "Greg Fields" < = EMAIL ADDRESS REMOVED = >
>>> To: "TEITAC Audio/Video Subcommittee" < = EMAIL ADDRESS REMOVED = >
>>> Sent: Wednesday, September 19, 2007 11:15 AM
>>> Subject: Re: [teitac-video] A modest proposal
>>>
>>>
>>>> Larry - thank you for putting this together.
>>>>
>>>> Quick questions:
>>>> 1) As per Andrew Kirkpatrick's feedback, are we confident that all
>>>> devices in scope can support opacity levels?
>>>>
>>>> 2) Note that these types of devices in scope will have their own
>>>> method for displaying and labeling the text sizes available on the
>>>> device, and the size parameters would be measurable and most likely
>>>> not defined as "smaller" or "larger". Should we perhaps alter the
>>>> user-controllable text size wording slightly to reflect this device
>>>> reality? The concept we may need to capture is that the
>>>> user-defined text sizing options are by default limited to those
>>>> size options available on a given device (or platform).
>>>>
>>>> Possible re-word (very open to wordsmith feedback):
>>>>
>>>> "adjustment of the text sizes available on the device to provide
>>>> users with multiple text display options."
>>

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