Last update: August 8, 2005
The numbers in the Failures column indicate problem reports in the Eclipse
Bugzilla database (http://bugs.eclipse.org/bugs).
The bug database has other PRs marked with the keyword "accessibility",
however these are minor and are not an issue in meeting the checklist requirements.
|
IBM Software Accessibility Checklist - Version 3.1 |
|||
|
1 |
Keyboard access |
Yes |
Comments |
|
1.1 |
Provide keyboard equivalents for all actions. |
Yes |
|
|
1.2 |
Do not interfere with keyboard accessibility features built into the operating system. |
Yes |
|
|
2 |
Object Information |
Yes |
Comments |
|
2.1 |
Provide a visual focus indicator that moves among interactive objects as the input focus changes. This focus indicator must be programmatically exposed to assistive technology. |
Yes |
89820 (SWT), 75384 (Compare) |
|
2.2 |
Provide semantic information about user interface objects. When an image represents a program element, the information conveyed by the image must also be available in text. |
Yes |
|
|
2.3 |
Associate labels with controls, objects, icons and images. If an image is used to identify programmatic elements, the meaning of the image must be consistent throughout the application. |
Yes |
|
|
2.4 |
When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements and functionality required for completion and submission of the form, including all directions and cues. |
Yes |
|
|
3 |
Sounds and Multimedia |
Yes |
Comments |
|
3.1 |
Provide an option to display a visual cue for all audio alerts. |
N/A |
Occasional use of system beep, which is handled by OS. |
|
3.2 |
Provide accessible alternatives to significant audio and video. |
N/A |
|
|
3.3 |
Provide an option to adjust the volume. |
N/A |
|
|
4 |
Display |
Yes |
Comments |
|
4.1 |
Provide text through standard system function calls or through an API (application programming interface) which supports interaction with assistive technology. |
Yes |
50646, 88777 (SWT), 100034 (UI) |
|
4.2 |
Use color as an enhancement, not as the only way to convey information or indicate an action. |
Yes |
Breakpoints use color to show their state: blue for enabled, clear for disabled. But this state is accessible via the breakpoint properties dialog. |
|
4.3 |
Support system settings for high contrast for all user interface controls and client area content. |
Yes |
63220, 71819, 97461 (UI), 75128 (Intro), 97600 (PDE) |
|
4.4 |
When color customization is supported, provide a variety of color selections capable of producing a range of contrast levels. |
Yes |
|
|
4.5 |
Inherit system settings for font, size, and color for all user interface controls. |
Yes |
|
|
4.6 |
Provide an option to display animation in a non-animated presentation mode. |
N/A |
|
|
5 |
Timing |
Yes |
Comments |
|
5.1 |
Provide an option to adjust the response times on timed instructions or allow the instructions to persist. |
Yes |
Cell editors in the Tasks view have timed interaction, but the Task Properties dialog is an accessible alternative. |
|
5.2 |
Avoid the use of blinking text, objects or other elements. |
Yes |
|
|
6 |
Documentation |
Yes |
Comments |
|
6.1 |
Provide documentation in an accessible format. Check using accessibility compliance tools. |
Yes |
|
|
6.2 |
Provide documentation on all accessibility features including keyboard access. |
Yes |
|
|
7 |
Verify Accessibility |
Yes |
Comments |
|
7.1 |
Test for accessibility using available tools. |
Yes |
Tested with MSAA tools and JAWS on Windows. |