Key Issues In Assuring That National Information Infrastructure
(NII)
in Classrooms is Accessible - (A 2-Page Quicksheet)


In assuring that NII deployments in classrooms are accessible there are three key areas that need to be addressed.
  1. Is the SOURCE MATERIAL Accessible?
    - (Responsibility of Content Producers, Web Sites, and Purchasing agents at schools)

  2. Are the TRANSMISSION MECHANISMS capable of transmitting the material without dropping the access features?
    - (Responsibility of the Internet Architects like W3C and Software Companies)

  3. Is the VIEWER/CONTROLLER technology (INCLUDING SOFTWARE) used to present the information to the user accessible / usable accessible?
    - (Responsibility hardware and software vendors and the Purchasing agents at schools)


1. SOURCE MATERIAL

Any material being developed needs to be flexible enough to allow access by people with disabilities. This includes videos, web sites, educational computer programs, reference materials, etc.

For each item or material:


2. TRANSMISSION SYSTEM

The wires used to bring NII information into a school (the Internet today) are not inherently inaccessible themselves. They just bring in bits of data and there is nothing much that will make them more or less accessible. The accessibility issues around the TRANSMISSION MECHANISMS fall into two categories.

1.) Where do the wires run?

2.) What data formats are used to transport the information. Do they support alternate modality presentation of information?


3. VIEWER/CONTROLLER TECHNOLOGY (INCLUDING SOFTWARE)

The technologies that are used to create or present information to the user must be accessible or the user with a disability will not be able to operate the technology to navigate through, create or view the information. Much of this access (or lack of access) is a function of the software used. Sometimes this software is provided along with or as part of the educational materials. In other cases (as with a web browser) one vendors software is used to view or present another vendors educational materials.

Again, as educational programs get more complicated and more interactive, built in accessibility usually provides the best access solution. Where this is not possible, then compatibility with assistive devices should be provided.

Key questions to ask regarding DIRECT ACCESSIBILITY (which does not require assistive technology) are:

If the Viewer/Controller Hardware and Software (or the source material) is not directly accessible and usable by people with one or another type of disability, then is it compatible with assistive technologies they may use to gain access to it?

Key questions regarding COMPATIBILITY with assistive technologies include:

WHAT DOES ACCESSIBLE MEAN?

Not all software can be made accessible to all people with all disabilities or combinations of disabilities. The question therefore is not an absolute "Is this software or feature accessible?" because no program or material will be accessible to all. Rather a more difficult pair of questions:

HOW TO ACHIEVE MAXIMUM ACCESSIBILITY?

Some strategies for maximizing the accessibility of your software and systems.

Prepared by Gregg Vanderheiden, Trace R & D Center, Univ. of Wisc. (http://trace.wisc.edu) 2/1/97



trace.wisc.edu
This document is hosted on the Trace R&D Center Web site. Please visit our home page for the latest information about Designing a More Usable World - for All.