[17] in Software Accessibility Project email archive
Minutes from meeting of 10/26
daemon@ATHENA.MIT.EDU (Kathleen Cahill)
Thu Oct 26 17:07:26 2000
Message-Id: <200010262107.RAA25812@melbourne-city-street.MIT.EDU>
Date: Thu, 26 Oct 2000 17:07:22 -0400
To: sw-access@MIT.EDU
From: Kathleen Cahill <kcahill@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Attending were: Jeff, Mary Ellen, Roberta, Barbara, Kathy, Jean, Nina
Kathy distributed a new draft of the Policy on Info. Technology
Accessibility. A few edits were suggested and Mary Ellen will post to the
web site (Kathy will email the document to her).
Nina talked with Ann Wolpert about the policy issue. Ann suggested
shopping it around to different departments to whom it would pertain, such
as HR, Libraries, Purchasing,etc... Jean brought up her concerns that a
lot of academic depts. are out there developing software for I-Campus or
under the d'Arbeloff grants, and also need to be educated. We may also
need to contact these groups as well. Kathy mentioned the web
accessibility policy and how a postcard announcing it was sent around. We
may not need to flood the mailboxes to that extent, but Nina suggested a
bottom-up lobbying effort may make the most sense, rather than just relying
on edicts from above. Barbara also mentioned bringing it to the attention
of Risk Management as well.
Guidelines -- we discussed adoption of the IBM guidelines. Kathy sent an
email to IBM asking for permission to use their guidelines. (I actually
found the correct person to write to and did it today!!) Each of the IBM
guidelines has a link to a page with a section on Rationale, Techniques and
Testing. Roberta thought these might be too much info for people. She
thought illustrations of the different guidelines would help. We were
trying to figure out how to make it simple but thorough. We may need to
include screen shots of accessible and inaccessible examples. Jean
suggested the Student Technology Consultants, who might be good for a
project like this. We also talked about how good design guidelines for web
and software are sometimes redundant, and maybe we should group the
guidelines for web and software, with different examples of each. Mary
Ellen, Jean and Kathy will meet on their own to discuss the guidelines and
examples.
Publicity: We will have an IAP presentation on this topic. We may also
want to develop "Quick Tips" cards as the W3C did with Web Accessiblity.
The cards could contain guidelines for software accessibility. We would
also need to do presentations for departments, such as the ones described
above who would be licensers, developers or purchasers of software. Level
of information needed would vary by role.
To do list:
Kathy to send draft of Policy to Mary Ellen to put up on the web page.
Mary Ellen, Jean and Kathy will meet to plan guidelines project for Student
Consulting Group.
Jean or Kathy (I forgot) will contact Student Technology Consultants
Jean will move ADA folder (Web and Software accessibility pages) to
web.mit.edu/accessibility
Jean will talk to Phil Long re: access issues for I-Campus and d'Arbeloff
projects
Next meeting is Nov. 9 at 10 AM in N42.
Thanks...if I forgot anything or have it wrong, please let me know.
Kathy
++++++++++++++++++++++++++++++++++++++
Kathy Cahill
MIT Adaptive Technology (ATIC) lab
77 Mass. Ave. 11-103
Cambridge MA 02139
(617) 253-5111
kcahill@mit.edu
