from http://www.sun.com index.html (fwd)

From: usmmmxbl@ibmmail.com
Date: Thu Feb 16 1995 - 13:31:38 PST


If you are on the TRACE CENTER list you have seen this, but since we
have discussed SUN workstations here, I thought it would be appropriate
to post the following:

Regards,
Steve Jacobson
  INTERNET: SOJACOBSON@MMM.COM
*** Forwarding note from I1305765--IBMMAIL 02/16/95 15:32 ***
Date: Thu, 16 Feb 1995 14:25:09 -0600
From: "Mark J. Senk WB3CAI" <senkmj@ptbma.usbm.gov>
To: Multiple recipients of list <uaccess_l@trace.wisc.edu>
Subject: from http://www.sun.com index.html (fwd)

I came across this on the SMI webserver and thought I'd pass it along.

   Information, like love, is worth little until you share it with someone.
Mark Senk (412) 892-6513 senkmj@ptbma.usbm.gov
U.S. Bureau of Mines Pittsburgh, PA 15236

---------- Forwarded message ----------
Date: Sun, 12 Feb 1995 05:04:12 -0500
From: SENK <senkmj@ptbma.usbm.gov>
To: senkmj@ptbma.usbm.gov
Subject: index.html

      [SUN MICROSYSTEMS, INC.] [SUN MICROSYSTEMS LABORATORIES, INC]

                          ABOUT ENABLING TECHNOLOGIES

   Earl Johnson
   Manager and Principal Investigator
   earl.johnson@eng.sun.com

   [IMAGE]

   Sun's investigations into developing accessible systems has found that
   designing to meet the needs of users with disabilities today helps
   make all users more productive, and strengthens the effectiveness of
   tomorrow's general technologies. Examples are speech recognition,
   text- to-speech, and interactive media.

   An early outcome from the investigations was the establishment of the
   Enabling Technologies (ET) project. ET is responsible for developing
   architectural strategies and solutions to benefit users with
   disabilities. An enabling technology is one which increases system
   access, system control, and overall task productivity for ALL users.
   This definition is used to identify areas within Sun where ET needs to
   influence product development.

   In general, Sun's ET activities are to:
     * Establish guidelines for developers on how to build accessible
       products;

     * Identify and test access solutions currently available for the
       user with a disability;

     * Establish functional requirements for then test and evaluate
       future bundled and third party access solutions;

     * Develop an accessible workstation which meets the requirements of
       Section 508 of the Federal Rehabilitation Act and the Americans
       with Disabilities Act;

     * Identify how Sun could be affected by the requirements found in
       the ADA and Section 508.

   We are currently targeting solutions for users with mobility and
   sensory (vision and hearing) disabilities. These efforts will lead to
   solutions, e.g., screen readers, which will be combined to address the
   needs of users with cognitive disabilities.

   Our approach has been to develop the system hooks, or APIs, that will
   attract and promote the development of bundled, third party and
   research-based access solutions. This approach insulates the access
   solution developer from the intricacies of our system and allows us to
   tap into the expertise that is currently available inside and outside
   of Sun.

   Examples of our access solution efforts include:

          Bundled--StickyKeys, which allows sequential single finger or
          pointer operation of multiple keystroke sequences such as
          Shift-m for M; for persons with physical disabilities.

          Third party--Speech recognition, which provides voice control
          of keyboard-based user interface control functions; aids all
          but blind users.

          Research--We are supporting and working with Georgia Institute
          of Technology on Mercator, which provides control of and access
          to screen contents and functions for blind users.

   [IMAGE]

   The ET home page also provides you with the ability to find out more
   information on:
     * Guidelines on building accessible software
     * Project accomplishments
     * Collaborative research projects
     * Additional reading
     * Guide dog FAQ
     * Information on agencies and conferences specializing in disability
       issues

   [IMAGE]

----------------------- End of Mail Text ---------------------
This item has been forwarded via SMTP from an Internet network
The SMTP (RFC 822) headers from the original item follow.

Received: from trace16.waisman.wisc.edu by ibmmail.COM (IBM VM SMTP V2R3)
   with TCP; Thu, 16 Feb 95 15:28:36 EST
Received: from (server@localhost [127.0.0.1]) by trace16.waisman.wisc.edu (8.6
.9/8.6.9) with SMTP id OAA21685; Thu, 16 Feb 1995 14:25:09 -0600
Message-Id: <Pine.3.88.9502122317.B36357-0100000@ptbma.usbm.gov>
Errors-To: wilson@trace.wisc.edu
Reply-To: uaccess_l@trace.wisc.edu
Originator: uaccess_l@trace.wisc.edu
Sender: uaccess_l@trace.wisc.edu
Precedence: bulk
X-Listprocessor-Version: 6.0 -- ListProcessor by Anastasios Kotsikonas
X-Comment: List for Discussion of Universal Access to Information Systems



This archive was generated by hypermail 2b29 : Sun Dec 02 2012 - 01:30:03 PST