Jump to: navigation, search

Difference between revisions of "Planning Council/Cross Project Teams/Accessibility"

(Recommendation to Planning Council)
(Meetings and Notes)
Line 19: Line 19:
  
 
== Meetings and Notes ==
 
== Meetings and Notes ==
 +
Meeting 10/15 9:00am US EDT
 +
Attendees: Tammy, Neil, Kentarou & Kaloyan
 +
 +
* reviewed the goal of this project
 +
* discussed which Accessibility standards each company is following, confirmed that all (involved in this meeting) are using the US Section 508.
 +
* Kentarou provided an overview of the incubator ACTF project: http://www.eclipse.org/actf/
 +
* The ACTF project needs to be enhanced more before it can be widely adopted by Eclipse projects.  Currently does not provide tooling for SWT. It currently supports html, flash content, similar function as inspect32...  Helios timeframe is to short to build in the additional function.
 +
* For a short term solution we believe it would be valuable to update the Accessibility guidance located at eclipse.org: http://www.eclipse.org/articles/article.php?file=Article-Accessibility/index.html#  This document was originally created by Tod Creasey in IBM, Tammy will contact Tod to see about getting this webpage updated.
 +
* Confirmed that each team is using the Software, Web & Documentation checklists.  Tammy will work on getting a copy of these checklists to possibly include in the 'Should do'/guidelines section of the release train/ emphasize/recommended . http://www-03.ibm.com/able/guidelines/index.html
 +
* Kaloyan is trying to locate an Accessibility rep to join him on the team
 +
* Will most likely break this up into two parts: short term/Helios: update guidance documentation and provide stripped down checklists.  long term goal: provide tools (possibly ACTF) to automate Accessibility checking during development.
 +
* will meet again on 10/20 9:00am US EDT
  
 
== Recommendation to Planning Council ==
 
== Recommendation to Planning Council ==

Revision as of 13:14, 16 October 2009

Accessibility Team

Members

Tammy Cornell, IBM
Kentarou Fukuda, ACTF Project
Neil Hauge, Oracle
Kaloyan Raev, SAP

Statement of Problem

Currently, many Eclipse Members have a business need to make sure software they consume from Eclipse meets certain Accessibility requirements. Besides just being a nice thing to do, it is often required to "prove" software is accessibility, in order to sell to certain markets or bid on certain contracts.

The "proof" often comes in the form of conducting certain tests and checks and completing a checklist, for long term documentation of what was done to ensure the software is accessible.

Currently, many Eclipse members have their own process and checklists for this accessibility work, but it would be simpler if there was one "Eclipse Accessibility Checklist" which would set the expectation for all Eclipse Projects ... at least all Eclipse Projects participating in the yearly, simultaneous release. And, of course, this "required item" for the yearly release can not be too burdensome for the Eclipse projects.

Our "required" item for Galileo simultaneous release was a 'should do' item, and stated as simply as "... should design and test for accessibility". So another way to state the problem, is whether or not there is a stronger requirement that would lead to a stronger, more demonstrable or measured statement about accessibility compliance.

Meetings and Notes

Meeting 10/15 9:00am US EDT Attendees: Tammy, Neil, Kentarou & Kaloyan

  • reviewed the goal of this project
  • discussed which Accessibility standards each company is following, confirmed that all (involved in this meeting) are using the US Section 508.
  • Kentarou provided an overview of the incubator ACTF project: http://www.eclipse.org/actf/
  • The ACTF project needs to be enhanced more before it can be widely adopted by Eclipse projects. Currently does not provide tooling for SWT. It currently supports html, flash content, similar function as inspect32... Helios timeframe is to short to build in the additional function.
  • For a short term solution we believe it would be valuable to update the Accessibility guidance located at eclipse.org: http://www.eclipse.org/articles/article.php?file=Article-Accessibility/index.html# This document was originally created by Tod Creasey in IBM, Tammy will contact Tod to see about getting this webpage updated.
  • Confirmed that each team is using the Software, Web & Documentation checklists. Tammy will work on getting a copy of these checklists to possibly include in the 'Should do'/guidelines section of the release train/ emphasize/recommended . http://www-03.ibm.com/able/guidelines/index.html
  • Kaloyan is trying to locate an Accessibility rep to join him on the team
  • Will most likely break this up into two parts: short term/Helios: update guidance documentation and provide stripped down checklists. long term goal: provide tools (possibly ACTF) to automate Accessibility checking during development.
  • will meet again on 10/20 9:00am US EDT

Recommendation to Planning Council