Jump to: navigation, search

Difference between revisions of "Platform Accessibility Testing"

(New page: This page describes some useful techniques and tools to test your Eclipse application for accessibility issues.)
 
 
Line 1: Line 1:
 
This page describes some useful techniques and tools to test your Eclipse application for accessibility issues.
 
This page describes some useful techniques and tools to test your Eclipse application for accessibility issues.
 +
 +
===Colours===
 +
*Switch to High Contrast mode. We support Windows XP High Contrast at 1152 x 764 as our test platform but others should be tested as well.
 +
*Test with stock themes. If you cannot get a good colour setup with them also test with reduced palette.
 +
 +
===Fonts===
 +
*Switch to High Contrast Mode as above.
 +
*Use large fonts and extra large fonts
 +
*Turn up monitor resoltion and lower DPI
 +
 +
===Accessible Listeners===
 +
*Many people test for accessibility using a commercial tool such as Window Eyes or JAWs. Any failures with these tools should be verified using something that calls the MSAA API (on Windows) such as inspect32.
 +
 +
[[Category:Platform UI]][[Category:Eclipse Project]]

Latest revision as of 13:45, 19 March 2008

This page describes some useful techniques and tools to test your Eclipse application for accessibility issues.

Colours

  • Switch to High Contrast mode. We support Windows XP High Contrast at 1152 x 764 as our test platform but others should be tested as well.
  • Test with stock themes. If you cannot get a good colour setup with them also test with reduced palette.

Fonts

  • Switch to High Contrast Mode as above.
  • Use large fonts and extra large fonts
  • Turn up monitor resoltion and lower DPI

Accessible Listeners

  • Many people test for accessibility using a commercial tool such as Window Eyes or JAWs. Any failures with these tools should be verified using something that calls the MSAA API (on Windows) such as inspect32.