Jump to: navigation, search

Difference between revisions of "Accessibility"

Line 1: Line 1:
 
= Accessible Eclipse Plug-ins  =
 
= Accessible Eclipse Plug-ins  =
  
Note: all the materials provided are useful, but note that some may predate the [http://www-03.ibm.com/able/news/eclipse_introduces_iaccessible2.html Eclipse accessibility API upgrade] which occurred with the release of Eclipse 3.6 (Helios) in June, 2010.
+
Note: all the materials provided are useful, but note that some may predate the [http://www-03.ibm.com/able/news/eclipse_introduces_iaccessible2.html Eclipse accessibility API upgrade] which occurred with the release of Eclipse 3.6 (Helios) in June, 2010.  
  
 
== Introduction  ==
 
== Introduction  ==
Line 25: Line 25:
 
If your issue isn't in the list, [https://bugs.eclipse.org/bugs/enter_bug.cgi file an Eclipse accessibility bug] (use the keyword "Accessibility").  
 
If your issue isn't in the list, [https://bugs.eclipse.org/bugs/enter_bug.cgi file an Eclipse accessibility bug] (use the keyword "Accessibility").  
  
For questions or more information, please [http://www.eclipse.org/swt/#contact use the forums] -- accessibility issues will be forwarded to the right person to answer them.
+
For questions or more information, please [http://www.eclipse.org/swt/#contact use the newsgroup] -- accessibility issues will be forwarded to the right person to answer them.

Revision as of 15:28, 16 November 2011

Accessible Eclipse Plug-ins

Note: all the materials provided are useful, but note that some may predate the Eclipse accessibility API upgrade which occurred with the release of Eclipse 3.6 (Helios) in June, 2010.

Introduction

Checklist

API

Bugs

Eclipse is an open source project. Testing, bug filing/triage, documentation and code contributions to the accessibility support are greatly appreciated.

When you run into an issue, check the Eclipse accessibility bug list.

If your issue isn't in the list, file an Eclipse accessibility bug (use the keyword "Accessibility").

For questions or more information, please use the newsgroup -- accessibility issues will be forwarded to the right person to answer them.