Color

Java™ checkpoint 4.1

Use color as an enhancement, not as the only way to convey information or indicate an action.

Rationale

Color can be most useful in highlighting actions for a visual display, however if a user cannot identify or distinguish colors they will not be able to make use of the information.The software needs to provide another way of making the information available. For example, asking users to press the green button is not useful if they can't distinguish the green button from other buttons on the screen. Instead put a label "Submit" on the green button and ask users to press the "Submit" button. Consequently the green will be an enhancement to the visual display and the "Submit" will provide the information to users who cannot identify or distinguish colors.

Development techniques

Use one or more of the following techniques to meet Checkpoint 4.1 from the IBM Java Accessibility Checklist:

Provide a brief text description of the object.e.g. A green button indicates that the information is correct and can be submitted and a red button indicates an error and the action is not ready to be submitted. Add text to the green button "Ready" and text to the red button "Error".
Include a graphic/character such as an asterisk by the item e.g. red and an asterisk indicates a document not read, black and no asterisk indicates a document has been read.
It is not sufficient to use additional attributes such as bold or italic. Using other attributes, such as bold and/or italic in addition to color to distinguish text, will help users who can not identify or distinguish colors, but does not help those users who use screen readers.

Testing techniques

Test the software to ensure that it complies with accessibility requirements.

Tools for testing this checkpoint
Windows techniques for testing this checkpoint

Tools

There are no test tools required to test this checkpoint.

Windows techniques

One or more of following techniques are required to verify this checkpoint:

	Action	Result
1	If the application uses color, visually inspect the screen and verify color is not the only way to identify or distinguish information.	Pass: All information is still meaningful if color is removed. For example, instructions to press the red submit button are accessible because the red button also includes the text label "Submit". Fail: Color is the only indication of what to do. For example, if the form uses the color red to highlight all required entry fields and does not use any other indication that it is required (e.g. asterisk), it is not accessible.
2	If the application uses color, print a copy of the screen in black and white to verify color is not the only way to identify or distinguish information.	Pass: All information is still meaningful if color is removed. For example, instructions to press the red button to submit a form are accessible because the red button also includes the text label "Submit". Fail: Color is the only indication of what to do on the screen. In the example below, the form uses the color red to highlight all required entry fields and does not use any other indication that it is required (e.g. asterisk). Required fields cannot be identified when viewed on a black and white screen shot of the screen.

Last updated February 15, 2008.

Checklist