Thread Subject: FW: Guideline Organization #2 -- SECOND PASS forcomment
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: Wed, May 16 2007 11:40 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Peter Korn: "Re: FW: Guideline Organization #2 -- SECOND PASSfor comment"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
Here is a revised draft of the ORGANIZATION APPROACH #2 based on comments
and feedback received this week.
Organization is shown with the non-hyphenated titles that are also in blue.
The titles that have hyphens or curly brackets are stand-in short names for
the actual provisions that are being worked on by the different groups.
So far we have heard only positive feedback on this new proposal as a whole.
If that continues through Friday, we will present this format as well as the
original format at the TEITAC meeting. So if you have concerns about this
format - or suggestions - please send by Friday so that we can finalize the
two formats (this and our other Linear/Characterization format) for
presentation next week at TEITAC.
Also look at our Working Draft Report to see if you have any comments.
Thanks
Gregg
-- ------------------------------
Co-Chair
_____
General Committee Recommendation for Reorganization
Format #2 5/16/2007
1 Overall Functional Performance Criteria
{Functional Performance Criteria Go Here}
2. Provisions for Product Hardware
All Products with Hardware
- Provide visual and either audio or tactile key status indicators
- If touchscreen or touch controls [and softkeys?] then provide non-touch
alternate
Advisory: - Make controls compatible with prosthetics
- Provide Alternative to biometric ID
- Use Standard ports
- Mechanism for connection of alternate input and output devices
If the Product has Physical Controls
- If products stand independently then controls meet ADAAG approach and
Reach Specs
- Controls meet ADAAG control specs.
- Tactilely Discernable without activation
- No require pinching, twisting of the wrist, or tight grasping.
- If Keyrepeat then adjustable
- Status of locking and toggle keys visual and auditory or tactile
If the Product has Standard Keyboard or Keyboard Interface
- Make Product Operable Using Only Input to Standard Keyboard interface (or
Keyboard equivalent)
If the product has Audio Output
- If speaker of product is held to ear then minimize hearing aid
interference
- If speaker of product is held to ear then provide hearing aid compatible
coupling
- Provide amplification for products in public places
- Standard Connector available for Audio Output
3. Software & General Provisions
All products
- Have no more than 3 flashes above safety thresholds
- No interference with built in Access Features
- Consistent use of images for controls, status, etc
- All visual information (display or labels) in auditory form in at least 1
mode
- Impose No Time limitations or make time limit adjustable
- If Interactive Voice Response (IVR) (Voicemail, Auto-attend, &
voicemenus etc.) provide no time limit or time limit adjustable.
- Make Any Key Repeat Delay & Rate Adjustable & Turn off (2 sec)
If the Product has Visual Output or Display
- Variety of Color & Font settings for Contrast
- Information not provided in color alone.
- At least 1 non-animated version available
- Moving text available static in 1 mode
- Provide highly visible keyboard focus and text cursors
- No override of display settings (if display includes audio then it cant go
here)
If Software runs on platform with Operating System that has AT Support
- All info and control avail to INTERNAL AT
- Provide Text through API / OS Text tools
- Focus Indicator Avail to AT (+clearly visible covered above)
If Software runs on "Closed" system (no AT Support)
- If closed to AT for any user group, make product fully usable by
that group without AT
If authoring tools (goes here if any?? )
4. Electronic Content Provisions (for products, training, electronic
documentation or services)
If Web Content
- {Web Content Provisions Go Here}
If a Content Format
- {New provisions from Web-Soft on Content Formats}
5. Additional Provisions for Audio-Visual Content or Players/Displays
If Audio and/or Video content
- Provide synchronized alternatives to synchronized audio and video
- AV Material is Captioned (Open or closed) {using format for that media}
- Provide Audio description of video {using format for that media}
- Captions & Audio Description User selectable unless Embedded in Video
If product (hardware or software) plays or displays AudioVideo
material
- Caption decode and Display supported
- Players/Displays support Audio Descriptions
(See applicable guidelines in other sections)
6. Additional Provisions for Real-time Voice Conversation Functionality (Was
Telecom but now includes VoIP)
- Provide Voice amplification
- Loud volume auto reset (+indicator + override)
- ( Proposed text conversation provisions would go here when finalized. )
- If not providing function itself then provide direct connect of
standard real-teim Text Terminal& mic toggle
- Support for standard text conversation signal
- Make IVR (Voicemail, Auto-attend, & IVR) work with Standard realtime
text formats
- Caller ID etc accessible to Blind & realtime text users
7. Information, Documentation and Support
Product Documentation and help
- Information and documentation is accessible (per #4) (And avail on Web?)
- Description of accessibility features is available
Support and E&IT related services
- Product support phone services are accessible
- Contact information is avail for access info
- Product Training (if part of product) is Accessible
X. Product Development Process (255 only)
Process guidance
- Include PWD throughout process (4 parts)
- Changes shall not decrease access
- Include access in design, devel, & fabrication
Gregg
------------------------
Gregg C Vanderheiden Ph.D.
Co-chair
- Next message in Thread: Peter Korn: "Re: FW: Guideline Organization #2 -- SECOND PASSfor comment"
- Previous message in Thread: None