Thread Subject: Re: 6.3e

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: Hoffman, Allen
Date: Thu, Jul 26 2007 10:10 AM

It may appear that way but I'll walk through it and lets see.

I make a DVD:
in DVD player with audio menu options it is usable.
In PC still accessible.

I make a web-file flash, etc.
i have to meet software/web requirements, so its accessible, and
doesn't need additional stand-alone audio menus.

Am I missing something?




Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Shannon
Rapuano
Sent: Thursday, July 26, 2007 11:47 AM
To: TEITAC Audio/Video Subcommittee
Subject: Re: [teitac-video] 6.3e

Allen, I understand and agree with the requirement for providing the
audio equivalents when the multimedia is closed like a DVD player.
However, this provision does not limit the requirement to those types of
environments.
As written, it would apply to all multimedia content. My concern is the
scope of the provision is too broad.


shannon
------------------------------------------------------------------------
------

Shannon Rapuano, IBM Accessibility Center
(727) 494-0782, Tieline: 273-3031
CLP Lotus Notes Application Developer R5

IBM Accessibility Center: http://w3.ibm.com/able Developer guidelines:
http://w3.ibm.com/able/devtest/index.html
Subscribe to the Showcasing Accessibility podcast:
http://w3.webahead.ibm.com/medialibrary/media_set_view?id=1092




"Hoffman, Allen"

<Allen.Hoffman@dh

s.gov>
To
Sent by: "TEITAC Audio/Video Subcommittee"

teitac-video-boun < = EMAIL ADDRESS REMOVED = >

= EMAIL ADDRESS REMOVED = .o
cc
rg


Subject
Re: [teitac-video] 6.3e

07/26/2007 09:46

AM





Please respond to

TEITAC

Audio/Video

Subcommittee

<teitac-video@lis

t.teitac.org>









Shannon:

Turn off your TV, and try and use a DVD in a DVD player when it contains
menus.



Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Shannon
Rapuano
Sent: Thursday, July 26, 2007 9:25 AM
To: TEITAC Audio/Video Subcommittee
Subject: Re: [teitac-video] 6.3e

Why would audio equivalents be required if the interactive elements are
accessible with a screen reader? We have many multimedia courses with
interactive elements that we work very hard to make accessible with
screen readers. The courses can be navigated with the keyboard and the
menu selections, buttons and other interactive elements are spoken with
the screen reader. As written, it sounds like this provision would
require making the course self-voicing so the interactive elements have
audio equivalents.

shannon
------------------------------------------------------------------------
------

Shannon Rapuano, IBM Accessibility Center






"Karen Peltz

Strauss"

<kpsconsulting@st
To
arpower.net> "TEITAC Audio/Video Subcommittee"

Sent by: < = EMAIL ADDRESS REMOVED = >

teitac-video-boun
cc
= EMAIL ADDRESS REMOVED = .o

rg
Subject
Re: [teitac-video] 6.3e



07/26/2007 06:32

AM





Please respond to

TEITAC

Audio/Video

Subcommittee

<teitac-video@lis

t.teitac.org>









Don't we typically use "audio" in situations like this? . . as in:

All "multimedia" containing interactive elements, such as menus for
selection and access to segments of the content, that are part of the
content MUST include AUDIO equivalents for menu selections.

Karen



----- Original Message -----
From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
To: "'TEITAC Audio/Video Subcommittee'" < = EMAIL ADDRESS REMOVED = >
Sent: Thursday, July 26, 2007 4:45 AM
Subject: Re: [teitac-video] 6.3e


> Verbal just means words. This email is verbal. The menus on screen
are
> verbal. (so is braille)
>
> I think you mean "vocal" or "spoken" or something. But verbal is
> wrong word if you want people who are blind to hear them.
>
>
> Gregg
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Larry
>> Goldberg
>> Sent: Wednesday, July 25, 2007 2:41 PM
>> To: TEITAC AV list
>> Subject: Re: [teitac-video] 6.3e
>>
>> Whitney,
>>
>> Looks like we have general agreement for the new "truncated"
>> language as indicated below. Can you post this in your doc?
>>
>> - Larry
>>
>>
>> Larry Goldberg wrote:
>>
>> > How would it work if we truncated the requirement like this?:
>> >
>> > 6.3-E - Interactive Elements
>> > All "multimedia" containing interactive elements, such as menus for

>> > selection and access to segments of the content, that are
>> part of the
>> > content MUST include verbal equivalents for menu selections.
>> >
>> > - Larry
>> >
>> >
>> > Hoffman, Allen wrote:
>> >
>> >> Larry Goldberg wrote:
>> >> 6.3-E - Interactive Elements
>> >> Recent Unresolved Discussion regarding 6.3-E - Interactive
>> Elements:
>> >> 6.3-E - Interactive Elements
>> >> All materials containing interactive elements that are part of the

>> >> content must comply with 1194.21 [a-z] as well as 1194.24 a-e.
>> >>
>> >> While I think this language points where we want to go, it doesn't

>> >> plainly say that for menus, audio equivalents must be provided as
>> >> focus moves. Note, this is really critical for when the
>> content is
>> >> coming from a closed media, or being used on a closed playback
>> >> device. there must be a simpler way to say this so that
>> this meaning
>> >> is clear. I think there may be distinction between
>> read-only media
>> >> content and more read/write interactive content here, for
>> example, a
>> >> flash e-learning course delivered with multimedia over the
>> web must
>> >> meet the content, web, and software standards, which in
>> theory include a/v requirements.
>> >> In the spirit of creating general function-based technical
>> >> requirements, then moving to any specific requirements for
>> narrowly
>> >> scoped subsets, I would like to prose that the 6.3E item is either

>> >> kept as is, and additional more media specific provisions
>> drafted, or
>> >> we incorporate some specific media-specific language into it.
>> >>
>> >> Here are some problems I see with just saying interactive elements

>> >> must meet software requirements:
>> >> They have to meet closed requirements primarily, as closed
>> media is
>> >> closed due to playback device primarily.
>> >> software contains requirements specifically related to
>> accessibility
>> >> services on platforms, these don't match reality of
>> playback systems
>> >> today.
>> >>
>> >> So:
>> >> rewrite of 6.3E might be:
>> >> 6.3-E - Interactive Elements
>> >> All "multimedia" containing interactive elements, such as
>> menus for
>> >> selection and access to segments of the content, that are part of

>> >> the content MUST include verbal equivalents for menu
>> selections, and
>> >> must comply with 1194.21 [a-z] as well as 1194.24 a-e.
>> >>
>> >> Note, this would make my concern plainly addressed if we then work

>> >> with web/software/content to nail down the final standards in that

>> >> section that have to be complied with more carefully.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 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, July 25, 2007 12:04 PM
>> >> To: TEITAC AV list
>> >> Subject: [teitac-video] AV Meeting today - 3pm ET
>> >> Importance: High
>> >>
>> >> Agenda:
>> >>
>> >> resolve 4-A:
>> >> 4. Additional Provisions for Audio-Visual Content or
>> Players/Displays
>> >> 4.1.A Caption Playback
>> >>
>> >> 6.3-E - Interactive Elements
>> >> Recent Unresolved Discussion regarding 6.3-E - Interactive
>> Elements:
>> >> 6.3-E - Interactive Elements
>> >> All materials containing interactive elements that are part of the

>> >> content must comply with 1194.21 [a-z] as well as 1194.24 a-e.
>> >>
>> >>
>> >> PHONE BRIDGE (supplied by Adobe):
>> >> Meeting id#: 107147
>> >> 1-877-220-5439 (US)
>> >> 1-800-64-219 (Australia)
>> >> 44-20-8608-1105 (London)
>> >>
>> >> Alternatively, dial into a local office and transfer to x69900
>> >> 353-1-433-6790 (Dublin) 81-3-5740-2600 (Tokyo)
>> >> 91-120-2444711 (Noida)
>> >>
>> >>
>> >> FEDERAL RELAY CONFERENCE CAPTIONING FOR July 25, 2007:
>> >> At the start time of the event, please login to your event by
>> >> clicking on this link:
>> >> http://www.fedrcc.us//Enter.aspx?EventID=759212&CustomerID=321
>> >> Alternately, you can visit http://www.fedrcc.us/ and input
>> your event
>> >> confirmation number, 759212.
>> >>
>> >> - Larry
>> >>
>> >>
>> >>
>> >>

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