What is the Overall CR Objective?

This is a six month initial exploration project. The objective is to operate in a triage mode and accomplish as much as possible toward ensuring that applications created using Java tools will be accessible to people with disabilities. In particular, the objective is to define those things that need to be done early in the process so that application developers will create applications which a) will be accessible, b) will be accessible when changes are made to Java tools, or c) will be accessible if special versions of the Java Tool Kit are created and used with the applications.

What are the Key Steps that will be Taken to Meet the Objectives?

1) Assembling a team of consumers, researchers and developers familiar with disability, the Web, and Java.

2) Identifying the key issues around disability access to Java-based applications.

3) Identifying known strategies for addressing the issues.

4) Prioritizing these strategies to identify which are most crucial to define and detail, and initiate action.

5) As a part of Step 4, identify those changes which must be done to the tools now versus those that could be done later.

6) Develop an initial set of developer guidelines.

7) Define the follow-on activities needed to refine understanding, test ideas, and create demonstrations of accessibility.

8) Provide some initial briefing and educational activity to Sun and its Java team on the issues and strategies, and work with them in identifying solutions.

Who is the Targeted Audience?

What is the Overall Context of the Strategy?

This project will be similar to trying to teach new fire fighting techniques to fire fighters who are in the midst of fighting a four-alarm blaze. The trick will be to figure how to define the issues and strategies in a very straightforward and compelling way to teams of people who are completely overloaded.

What Are the Deliverables?

1) A report in two parts
Part 1 on major disability issues identified.
Part 2 on suggested strategies classified both by importance and urgency.
2) Guidelines for developers of Java-based applications.

3) Awareness education and training session at Sun on the issues and their relation to the use of Java applications by all users, including power users.

4) Publication of the final report of this project will be made at the conclusion of the project. The University will provide SUN with a copy of the final report in advance of the proposed publication date and grant SUN 30 days for review and comment. The working copy of documents for this project will be available throughout the project on the internet at trace.wisc.edu as part of the process of getting external comments.

What are the Major Milestones and When Do They Happen?

First gathering of experts at the Conference on Technology and Disability, California State Universith Northridge, March 21-23, 1996.

Second meeting at RESNA June 1996.

Establishment of on-line collaborative working environment 20 days post contract signing.

First overview of issues and strategies within 60 days post contract.

Briefing visit to Sun within 120 days post contract.

Second release of issues and strategies document 5 months post contract.

Report on proposed further actions - 5 months post contract.

Release of formal report to Sun for review and comment - 5 months post contract.

Final release of report. 6 months post contract.

What will be the Results of Doing the CR?

Sun Microsystems and developers will have a much better idea of strategies whey can implement to maximize the usability of their applications by all potential users.