| [an error occurred while processing this directive] |
 |
Use this checklist for:
- Java 2 or later applications
Understanding Accessibility
If you are new to accessibility, review "Understanding Accessibility"
before completing the checklist.
IBM Java Accessibility Checklist
Techniques pages, accessed via the link in each checkpoint, may contain more recent updates than the checklist itself. Be sure to review the techniques pages for the latest accessibility guidance. For convenience in completing the Java accessibility checklist, save this page and edit the HTML file.
IBM Java accessibility checklist - version 3.1
|
| 1 |
Keyboard Access. |
Yes No
Planned
N/A |
Comments |
| 1.1 |
Provide keyboard equivalents for all actions. |
|
|
| 1.2 |
Do not interfere with keyboard accessibility features built into the operating system. |
|
|
| 2 |
Object information. |
Yes No
Planned
N/A |
Comments |
| 2.1 |
Implement the Java Accessibility API by:
- using the Java Foundation Classes
(JFC) / Swing components
and/or
- following the guidelines for "
Building Custom Components" when extending the Java Foundation
Classes and when implementing the Java Accessibility
API on custom components. |
|
|
| 2.2 |
Set the focus. |
|
|
| 2.3 |
Set the name on all
components and include the description on
icons and graphics. If an image is used to identify
programmatic elements, the meaning of the image must be consistent throughout
the application. |
|
|
| 2.4 |
Associate labels with controls, objects, and icons. |
|
|
| 3 |
Sound and multimedia. |
Yes No
Planned
N/A |
Comments |
| 3.1 |
Provide an option to display a
visual cue for all audio alerts. |
|
|
| 3.2 |
Provide accessible alternatives to significant audio and video. |
|
|
| 3.3 |
Provide an option to adjust the volume. |
|
|
| 4 |
Display. |
Yes No
Planned
N/A |
Comments |
| 4.1 |
Use color as an enhancement, not as the only way to
convey information or indicate
an action. |
|
|
| 4.2 |
Support system settings for high contrast for all user interface controls and client area content. |
|
|
| 4.3 |
When color customization is supported, provide
a variety of color selections capable of producing a range of contrast levels. |
|
|
| 4.4 |
Support system settings for size, font and color for all user interface controls. |
|
|
| 4.5 |
Provide an option to display animation in a non-animated presentation mode. |
|
|
| 5 |
Timing. |
Yes No
Planned
N/A |
Comments |
| 5.1 |
Provide an option to adjust timed responses or allow the instruction to persist. |
|
|
| 5.2 |
Avoid the use of blinking text, objects, or other elements. |
|
|
| 6 |
Documentation. |
Yes No
Planned
N/A |
Comments |
| 6.1 |
Provide documentation in an accessible format. |
|
|
| 6.2 |
Provide documentation on all
accessibility features, including keyboard access, as part of the regular product documentation. |
|
|
| 7 |
Verify accessibility. |
Yes No
Planned
N/A |
Comments |
| 7.1 |
Test for accessibility using available tools. |
|
|
©2001, 2002 IBM Corporation
Resources
The "IBM Guidelines for Writing Accessible Applications Using 100% Pure Java" are available as a separate document. This is the industry's first
set of 100% Pure Java application development guidelines for accessibility.
References
Some additional references on Java accessibility.
|
|
[an error occurred while processing this directive]
