W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2001

Re: Process/Procedure for Accessibility Testing of Software

From: Jean Foster <jfoster@world.std.com>
Date: Wed, 7 Mar 2001 15:33:20 -0500
Message-ID: <001d01c0a745$d9af4be0$6401a8c0@echo>
To: <w3c-wai-ig@w3.org>, "Kynn Bartlett" <kynn@reef.com>
Hi Kynn,

Look at IBM's software accessibility information. It's quite extensive.
I've found the Microsoft software accessibility guidelines to be very much
geared to developers writing applications for Windows.

The IBM Accessibility Center:

At MIT we are in the process of creating a software accessibility policy,
guidelines and recommendations for both software purchasers and developers
and are referring to the IBM guidelines.  We are combining these with our
Web access policy and recommendations.  So many applications these days have
Web front ends that the line is getting blurry. WGBH/NCAM has also released
great guidelines for accessible software for education at:


The best resource with links to these sites and more is the Trace page at:


Sun  has info for developers about software accessibility at:


----- Original Message -----
From: "Kynn Bartlett" <kynn@reef.com>
To: <w3c-wai-ig@w3.org>
Sent: Wednesday, March 07, 2001 5:55 AM
Subject: Process/Procedure for Accessibility Testing of Software

> Hi folks -- anyone got any pointers to references/material on how
> to test specific pieces of software to see if they are
> "accessible" (for common definitions of the word)?  I need to gather
> some things to show my QA/testing folks that they can understand.
> --Kynn
> --
> Kynn Bartlett <kynn@reef.com>
> Technical Developer Liaison
> Reef North America
> Tel +1 949-567-7006
> _________________________________________
> _________________________________________
> http://www.reef.com
Received on Wednesday, 7 March 2001 15:33:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:11 UTC