[50] in Software Accessibility Project email archive
Software Accessibility Project Report
daemon@ATHENA.MIT.EDU (Kathleen Cahill)
Fri Jun 29 14:55:35 2001
Message-Id: <200106291855.OAA08940@melbourne-city-street.mit.edu>
Date: Fri, 29 Jun 2001 14:57:18 -0400
To: delivery@MIT.EDU
From: Kathleen Cahill <kcahill@MIT.EDU>
Cc: kcahill@MIT.EDU, sw-access@MIT.EDU, ganderso@MIT.EDU
Mime-Version: 1.0
Content-Type: multipart/alternative;
types="text/plain,text/html";
boundary="=====================_6472229==_.ALT"
--=====================_6472229==_.ALT
Content-Type: text/plain; charset="us-ascii"
The Software Accessibility Policy and Guidelines moved from Integration into
Delivery once the actual policy and guidelines were finalized in May. The
full
project team met once more (May 10th) to finalize the language of policy and
guidelines, which are located at http://web.mit.edu/atic/www/sw/ .
In reviewing the policy and guidelines, the team decided that we would include
examples of accessible web design as well as the already existing examples of
accessible software design to clarify the guidelines. Right now, the focus is
on publicizing the guidelines as well as continuing support to purchasers and
developers. The publicity plan includes:
*Articles in Tech Talk, I/S Newsletter (May-June)
*Planned articles for Athena Insider, Faculty Newsletter
*Presentations to groups around campus, possibly IT Partners and ITAG
luncheons.
*Quick Starts on Web and Software Accessibility offered monthly
The ATIC lab and its staff will be available to answer developer/purchaser
questions regarding accessibility of products. It is also hoped that these
issues may arise during reviews with ITAG or Usability Team.
Kathy Cahill will be updating the project notebook and closing out the project
in July. Support and publicity will be ongoing.
Key Learnings:
Having developers on the team for feedback and clarification helped
immeasurably.
Clarifying our audiences helped in creating information that was (hopefully)
clear and understandable.
Having a technical writer (Mary Ellen Bushnell) was key in conveying sometimes
complex information.
Policy/legal input from Disabilities Services staff was also key in knowing
how
to create language that satisfies the law.
I would like to thank our project team members:
Roberta Crumrine, SSIT
Jim Repa, I/S
Jeff Harrington, Alumni
Jean Foster, I/S
Barbara Roberts, Disabilities Services Office
Mary Ellen Bushnell, I/S
Nina Davis-Millis, Libraries
Thank you,
Kathy
--=====================_6472229==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
The Software Accessibility Policy and Guidelines moved from Integration
into Delivery once the actual policy and guidelines were finalized in
May. The full project team met once more (May 10th) to finalize the
language of policy and guidelines, which are located at
<a href="http://web.mit.edu/atic/www/sw/" eudora="autourl">http://web.mit.edu/atic/www/sw/</a>
. <br>
<br>
In reviewing the policy and guidelines, the team decided that we would include examples of accessible web design as well as the already existing examples of accessible software design to clarify the guidelines. Right now, the focus is on publicizing the guidelines as well as continuing support to purchasers and developers. The publicity plan includes:<br>
<br>
*Articles in Tech Talk, I/S Newsletter (May-June)<br>
*Planned articles for Athena Insider, Faculty Newsletter<br>
*Presentations to groups around campus, possibly IT Partners and ITAG luncheons.<br>
*Quick Starts on Web and Software Accessibility offered monthly<br>
<br>
The ATIC lab and its staff will be available to answer developer/purchaser questions regarding accessibility of products. It is also hoped that these issues may arise during reviews with ITAG or Usability Team.<br>
<br>
Kathy Cahill will be updating the project notebook and closing out the project in July. Support and publicity will be ongoing.<br>
<br>
<b>Key Learnings</b>:<br>
<br>
Having developers on the team for feedback and clarification helped immeasurably.<br>
Clarifying our audiences helped in creating information that was (hopefully) clear and understandable.<br>
Having a technical writer (Mary Ellen Bushnell) was key in conveying sometimes complex information.<br>
Policy/legal input from Disabilities Services staff was also key in knowing how to create language that satisfies the law.<br>
<br>
I would like to thank our project team members:<br>
<br>
Roberta Crumrine, SSIT<br>
Jim Repa, I/S<br>
Jeff Harrington, Alumni<br>
Jean Foster, I/S<br>
Barbara Roberts, Disabilities Services Office<br>
Mary Ellen Bushnell, I/S<br>
Nina Davis-Millis, Libraries<br>
<br>
Thank you,<br>
Kathy<br>
<br>
<br>
<br>
<br>
</html>
--=====================_6472229==_.ALT--
