For those working on technology access, here is a model policy on software
access.

kelly

>From the web page http://tap.orst.edu/Policy/soft.html

        Oregon State University Software Access Guidelines

Purpose

The universal access to information is a part of the
University's ongoing commitment to establishing a barrier free
learning community at Oregon State. These guidelines have been
established as a part of this commitment, and to meet the
ethical and legal obligations that we have under Sections 504
and 508 of the Rehabilitation Act of 1973, 29 U.S.C. 794 & 794d,
as amended. This obligation is to insure accessibility to the
programs and activities of the University for individuals with
disabilities, and specifically the Section 508 provisions that
require that electronic and information technologies be
accessible. In the acquisition of information technology
hardware and software it is necessary that these guidelines be
complied with.

The purpose of this document is to provide a set of guidelines
for vendors to the University, and those individuals responsible
for overseeing the purchase of information technology. It
provides the minimally acceptable standards for software
accessibility that applications must meet if they are to be
purchased and used by University programs. These guidelines are
presented to demonstrate the range of disabilities that must be
addressed by software designers and developers when providing
software to the University community. The guidelines are based
on proven techniques for the design of universally accessible
software that can be used by individuals with and without
disabilities. Software that is to be considered for use by the
University must comply with these guidelines at the time of
acquisition and be compatible with the accessibility tools, both
hardware and software, in use by individuals with disabilities
at the University.

While these standards present the minimally acceptable
standards, software designers and developers are strongly
encouraged to maximize the accessibility of their products for
universal access. If assistance is required, or more specific
recommendations sought please contact the Technology Access
Program at 737-7307, E-Mail: Technology Access Program

Access Specifications

Keyboard Access:

1. The software program must provide keyboard equivalent
commands for all the functions of the application. All actions
that are required or provided by the program must be accessible
by keystrokes. This includes, but is not limited to, mouse
actions, buttons, scroll windows, text entry fields and pop-up
menus.

2. Clear and precise instructions for the use of the keyboard
equivalents will be provided as part of the user documentation.

3. The software must provide logical tabbing order between text
entry fields.

4. The use of keystrokes must be logically progressive. (i.e.:
down arrow followed by the enter key)

5. The software will not interfere with any existing
accessibility features built into the operating system.

6. Avoid timed response if possible. If timed response is
required, the user must be able to modify the timing parameters.

7. Visual and auditory prompts for control keys status is
encouraged.

Icons:

1. All icons must have text labels associated or the program
must allow the user to select text only buttons.

2. Icon use must be consistent throughout the application.

3. Pull-down menus equivalents must be provided for all Icon
functions.

4. Keyboard access to pull-down menus must be provided.

5. Painted or graphic text is not accessible, provide standard
system text for all text elements.

Sounds:

1. A visual equivalent must be provided for all audio alerts.

2. Existing operating system sound features must be supported.
(i.e.: Win95 show sounds)

3. Allow the user to disable or adjust sound volume.

4. Any information that is presented in an audio format, must
also allow for the user to access a real-time text description.

Display:

1. Color coding as the sole means of conveying information must
not be used. An alternative or equivalent method must be
available.

2. The application must support user definable color settings
system wide. Inverted text color must be available as an
alternative to highlighting.

3. Patterned backgrounds must not be used behind text or
important graphics.

4. The user must be able to override default fonts for printing
and text display.

5. The user must be able to adjust or disable flashing,
rotating, or moving text to the extent that it does not
interfere with the use of the application.

Field Labeling:

1. The text descriptions or labels for data fields must be
placed next to the field. The association must be clearly and
logically defined.

Documentation:

1. All manuals and documentation must be available in electronic
format as an ASCII text file. This must include text
descriptions for all charts, graphs, pictures, and graphics.

2. The user must have the ability to output any report or print
job in electronic format and an ASCII text file.


 This document is a publication of the Technology Access Program
  at Oregon State University. It may be distributed so long as
proper credit is given to the original source. This is a working
 document and as such is subject to revision. Please contact the
Technology Access Program if you have any comments or questions.

----------
End of Document


VICUG-L is the Visually Impaired Computer User Group List.
To join or leave the list, send a message to
[log in to unmask]  In the body of the message, simply type
"subscribe vicug-l" or "unsubscribe vicug-l" without the quotations.
 VICUG-L is archived on the World Wide Web at
http://maelstrom.stjohns.edu/archives/vicug-l.html