Thread Subject: Re: Multimedia discussion - Proposed 24(f)

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: Gregg Vanderheiden
Date: Thu, Mar 08 2007 10:35 AM

Closed isn't a product type



Neither is functional performance



Rest are good sort items. Plus more that people are asking for.




Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman, Allen
Sent: Thursday, March 08, 2007 10:55 AM
To: TEITAC Audio/Video Subcommittee
Subject: Re: [teitac-video] Multimedia discussion - Proposed 24(f)

I agree with you Andrew, but have considered this more from the perspective
of something like the tool Gregg created where you can see scope for each
standard in an organized fashion. so for example having a table contained
in the standards with scope for each one clearly marked might help.



so, for example:



We could use a typographic convention to identify categories:

[s] software/operating systems

[w] web

[t] telecomm

[v] video...

[c] closed

[d] desktop/portable/other

[f1-x] functional performance



So an item might look like:



[swtvc] When software is designed to run on a system that has a keyboard....



To me a wide-narrow sort order would make the best presentation to quickly
pick out items one would be most likely to need, but I'm certain we don't
need to think about this to that level.



I think adding scoping data would be helpful to many, and before we are done
would be a good thing to make sure we all are on the same page regarding how
the committee's work is to be completed.







Allen Hoffman -- 202-447-0303






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: Thursday, March 08, 2007 11:26 AM
To: TEITAC Audio/Video Subcommittee
Subject: Re: [teitac-video] Multimedia discussion - Proposed 24(f)

I'll post my main objection to this, which is not an objection to the idea
that this content needs to be accessible, but that I would far prefer that
there be a clear mechanism for developers and evaluators to know what 508
standards they need to think about. I'm concerned that we can't come up
with enough cross references to address everything. For a DVD, we might
need to cross reference the "closed" standards also.



I'd like to see a decision tree at the top of the standards -



1. Does your product have audio or video? if yes, apply 1194.24 standards
and go to question 2.

2. Does your product have interactive elements? If so, go to question 3, if
not go to question 5.

3. Is your product operating on a "closed system"? If so, apply the 1194.##
standards for closed systems. If not, apply 1194.21 standards for software.
Proceed to question 4.

4. [and so on]



Does this seem possible?



AWK




_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jessica M. Brodey
Sent: Thursday, March 08, 2007 11:00 AM
To: 'TEITAC Audio/Video Subcommittee'
Subject: Re: [teitac-video] Multimedia discussion - Proposed 24(f)

My apologies for re-sending this - my initial email contained a typo that
created confusion . . . After much discussion with a number of members on
this subcommittee, we are proposing a new section 24(f) with the following
language to address the concerns I have been raising on the conference calls
about multimedia elements in productions:



24(f) If the production includes interactive elements that are part of the
content, compliance with 1194.21 a-z is required.



Essentially, at issue are productions that contain more than merely audio
and video elements - they may contain elements of user choice that require
either data entry or user selection of different clips or scenarios. As a
result, it is critical for end-users to have full access to all elements in
the production, not just the audio and the video elements. These
productions may be played strictly on DVD players, or used in connection
with a computer, or broadcast over the Internet. These productions are
particularly common in educational/instructional settings. In our
discussions, we determined that these productions should be treated as
software, and as such, we decided to clearly indicate that to "close the
loophole" and guide the developers back to the software section.



Jessica Brodey

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