Thread Subject: Re: GENERAL WG-ReorgProposal-FORMAT2-5-17-07.doc

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: terry.weaver@gsa.gov
Date: Fri, May 18 2007 2:05 PM

I think as long as it is clear that the term documentation also understood
to include electronic documentation, then this is fine. I think the
connecting thought is that the standards under content will need to be
applied to 7 a.

For 4b - could we say Content for non-web formats (e.g., documents from
word processing, spreadsheet, presentation and similar applications)? I
don't like non-web as description but I want to point to the host of other
outputs created by applications.




"Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
Sent by: = EMAIL ADDRESS REMOVED =
05/18/2007 02:31 PM
Please respond to
"TEITAC General Interface Accessibility Subcommittee"
< = EMAIL ADDRESS REMOVED = >


To
"'TEITAC General Interface Accessibility Subcommittee'"
< = EMAIL ADDRESS REMOVED = >
cc

Subject
Re: [teitac-general] GENERAL WG-ReorgProposal-FORMAT2-5-17-07.doc






Andrew â comments below marked GV:

EVERYONE â if no one has a problem I will remove the word âELECTRONIC
DOCUMENTATIONâ from #4.


1) Why does #4 reference documentation? It seems like documentation can
refer from #7 to #4 on its own.
GV: This came out of our second last meeting with other suggested edits.
But it looks like your suggestion should work. If no one objects we
will remove the words from #4âs title.

2) I still don't know what a "content format" is. We need a lot more
clarity in this area.
GV: That is a new topic in the Software Group. They asked that we
reserve a place for them to put their work when done. (there was no
counterpart in the old 508) .

3) I really like the organization of the hardware requirements in #2. I'd
be in favor of moving 1194.24 a and b into the hardware group's domain and
it would fit well here, although there are software decoders for
captioning also...
GV: You might bring that up with your AV group. The software part is a
question of course. That might mean it should go into Software & General
Behavior. The rest of AV might then become content. But that is all
beyond what would be editorial which is all we can do at this point. So if
it is ok with you â weâll wait on those changes until the proper groups
can consider this.


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



From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: Friday, May 18, 2007 12:11 PM
To: TEITAC General Interface Accessibility Subcommittee
Subject: Re: [teitac-general] GENERAL WG-ReorgProposal-FORMAT2-5-17-07.doc
Comments:
1) Why does #4 reference documentation? It seems like documentation can
refer from #7 to #4 on its own.
2) I still don't know what a "content format" is. We need a lot more
clarity in this area.
3) I really like the organization of the hardware requirements in #2. I'd
be in favor of moving 1194.24 a and b into the hardware group's domain and
it would fit well here, although there are software decoders for
captioning also...

AWK



From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
Vanderheiden
Sent: Friday, May 18, 2007 1:02 AM
To: 'TEITAC General Interface Accessibility Subcommittee'
Subject: [teitac-general] GENERAL WG-ReorgProposal-FORMAT2-5-17-07.doc


Here is the latest version based on comments on list. (pasted below and
attached)

Please submit and final comments before Noon Friday so we can finalize
this and send on in advance with our report.


Have adopted the format the editorial group used since it separates the
structure from the provision wording. Title changes are marked with ***
and are in green.
There is an earlier structure (Format #1) also on the table which we have
not formally removed so it will be presented as well. But this one seems
to be the one that resonates with most people. If it doesnât resonate with
you â please comment on the list right away.
Both versions can be found on the TEITAC wiki at
http://teitac.org/wiki/Linear_Sortable_Format.


General Committee Recommendation for Reorganization
Format #2 (as of 17 May 2007)

1. Overall Functional Performance Criteria
{Functional Performance Criteria go here}
2. Provisions for Hardware Aspects of Products ***
2a. All Products with Hardware
{Hardware Requirements that apply to all products go here: tactile key
indicators, standard ports and connections for alternative input/output
devices and alternative to biometric ID}
2b If the Product has Physical Controls
{Requirements for physical controls go here: ADAAG approach and reach
specs for products that stand independently, ADAAG control specs for
tactilely discernable, pinch/twist/grasp, repeat and status indication}
2c. If the Product has Standard Keyboard or Keyboard Interface
{Requirements for keyboard operation}
2d. If the product has Audio Output
{Requirements for audio output: connectors, amplification, compatibility
with hearing aids}
3. Software & General Behavior Provisions ***
3a. All products
{Requirements that apply to all products: equivalence for visual
information (active and passive), consistent use of images, no
interference with access features, time/repeat adjustments, flashing,
etc.}
3b. If the Product has Visual Output or Display
{Requirements relating to active display of information: color, moving
text or animation, visible focus/cursors, no override of display settings}
3c. If Software runs on platform with Operating System with AT Support
{Requirements for software (and driver) support for assistive technology}
3d. If Software runs on âClosedâ system (no AT Support)
{Requirements to make products that are closed to any type of AT usable
without that AT}


4. Electronic Content Provisions
(for products, training, electronic documentation or services)
4a. If Web Content
{Web content requirements}
4b. If a Content Format
{Requirements for content formats}
4c. Additional requirements for Web Content Authoring Tools ***
{Additional Requirements for software tools specifically designed to
author web content } (MOVED FROM 3e) ***
5. Audio-Visual Content or Players/Displays
5a. If Audio and/or Video content
{Requirements for AV content: captioning, audio description, and
synchronized alternatives for audio and video with interaction.}
5b. If Product (hardware or software) Plays or Displays A-V Material
Requirements for support for captions, descriptions and cross-ref to other
applicable requirements}
6. Provisions for Real-time Voice Conversation Functionality
(Additional provisions for telecom, including VoIP)
{Requirements for voice conversation: applications, auto-reset, text with
voice conversations, IVR, Caller ID and alternative support for
connections for text terminal/mic toggle}
7. Information, Documentation and Support
7a. Product Documentation and help
{Requirements for access to and content of documentation and help}
7b. Support and E&IT related services
{Requirements for access and availability of support and training}
X. Product Development Process (255 only)
{Process guidance, including PWD, access in design, development &
fabrication, no decrease in access}

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