Re: [SEC508] TEITAC requirements by disability

[Gregg Vanderheiden <gv@trace.wisc.edu>]

there was one in the back of the TEITAC report but it has errors.

it was a mapping to the Functional Performance Criteria - which are essentially (but not exactly) by disability

http://www.access-board.gov/sec508/refresh/report/#83

If I remember right were known errors in it but there wasn’t time to correct them. 

If people want to look at it and send errors we will compile a corrected version for everyone. 

Perhaps we will add it to the filter tool

http://trace.wisc.edu/filter 

Gregg

-----------------------

Gregg Vanderheiden Ph.D.

Director Trace R&D Center

Professor Ind and Biomed Engr

University of Wisconsin-Madison

 

On Mar 24, 2009, at 2:05 PM, Phill Jenkins wrote:

Does anyone have a spreadsheet of the TEITAC requirements by disability?

Has anyone summarize the requirements listed in SubPart C (AKA provisions or checkpoints) into a sortable spreadsheet, something like this?
REQUIREMENT                DISABILITY
1-A Closed Functionality                All
1-D Audio Information                Deafness, Hard of Hearing
...

The TEITAC report includes details in SubPart C for each requirement which includes a list of the disabilities that would benefit from meeting the checkpoint. These requirements are part of the report TEITAC recommended to the U.S. Access Board to refresh the 508 standards. The final report is in a slightly harder to use format than a summarized sortable spreadsheet would be.  

See SubPart C http://www.access-board.gov/sec508/refresh/report/#65  

Each requirement (think checkpoint) includes "Additional Information" which lists the Disabilities affected.  For example, provision #1-A is listed below and includes "Disabilities: All". #1-D includes Disabilities: Deafness, Hard of Hearing".  

1. General Technical Requirements

1-A: Closed Functionality
If any functionality of a product is closed for any reason including policy constraints or technical limitations then that CLOSED FUNCTIONALITY must be made available to and operable by people with disabilities within the product itself. As a result, the following provisions would not apply to the CLOSED FUNCTIONALITY:

• 2.1-E - Connector or Connection Language
• 3-F - All Non-Text Objects
• 3-G - Human Language
• 3-H - Language of Parts
• 3-N - Link Purpose
• 3-O - Information and Relationships
• 3-P - User Interface Components (no consensus)
• 3-Q - Disruption of Access Features
• 3-U - AT Interoperability (partial consensus)
• 3-V - Accessibility Services
• 3-VV - Assistive Technology (no consensus)

Additional Information

• Text from Self Contained, Closed
• Source: {508}1194.25(a)
• Testability: Expert evaluation
• Disabilities: All

<clip>

1-D: Audio Information
Products must provide a mode in which audio is not the only means of conveying information, indicating an action, or prompting a response.
Note:  Before implementing a solution, please review the introductory material on the differences between Section 255 and Section 508, as they treat assistive technology (AT) solutions differently.

Additional Information

• Text from Self-Contained/Closed
• Source: {255}1194.43(d)
• Testability: Expert evaluation
• Disabilities: Deafness, Hard of Hearing

Regards,
Phill Jenkins,
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able
U.S. Access Board
http://www.access-board.gov/