Lotus Notes checklist

Checkpoint 4.2: Using color for enhancement

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


Applicable user interfaces

This checkpoint only applies to Lotus Notes applications viewed through the Notes client.

Note: Applications that support both the Notes client interface and the Web interface must complete both the Web checklist and the Lotus Notes checklist. When completing the Web checklist, related techniques and examples for Domino applications are found in Web checkpoint 1.4a – Use of Color.


Rationale

If an application conveys information by color alone, users who cannot identify or distinguish colors will not be able to make use of the information. For example, asking users to click the red button is not useful if they can't distinguish the red button from other buttons on the screen. The application needs to provide another way of making the information available.

An image with insufficient foreground and background color contrast may also cause problems for some users. An image containing light text on a dark background or dark text on a light background would provide good contrast. Users have no control over the color or contrast of images that contain text.


Required development techniques

Use one or more of the following techniques to meet Checkpoint 4.2 from the Lotus Notes Accessibility Checklist:

  1. In addition to using color, provide a brief text description. In the example below, the list item displayed in red indicates a racer who made the Olympic team. This item is also displayed in bold text as a redundant cue to the red color. Even though there is an additional cue besides the color, a screen reader would not provide this information to the user.

    These are the results of the race. Racers listed in red also made the Olympic team.
    One method of correcting this example is to add explanatory text to each item as follows:

    These are the results of the race. The second place finisher, highlighted in red, also qualified for the Olympic team.
  2. It is not sufficient to use attributes such as bold or italic in addition to color. While these attributes may provide additional information to users who cannot identify or distinguish colors, the attributes do not provide sufficient information for someone using a screen reader. Include a character such as an asterisk in addition to color. For example, in Lotus Notes, unread documents are displayed in the color red and with an asterisk.

    Screen shot from Lotus Notes Mail showing red line and asterisk for unread mail, and black with no asterisk for read mail


Recommended development techniques

The techniques above are required; the following techniques are recommended to enhance accessibility:

  1. Do not use graphics files as a background for a form. While this may add to the visual appeal of the form for some users, the background may make it difficult or impossible for some users with visual impairments to read the data on the form. Many users need high contrast between the background and foreground objects in order to read the documents. To enable users to turn off patterned backgrounds:
  2. If an image contains text, use either light text on a dark background or dark text on a light background to provide good contrast. For example, the first image on the left uses good contrast, light text on a dark background, while the second image on the right uses poor contrast, medium blue text on a slightly darker blue background.

    good contrast example - white text on black backgroundbad contrast example - blue text on a dark blue background

There are many free resources that provide information about effective color contrast including:


Required test techniques

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

Tools

No tools are required to test this checkpoint.

Techniques


The following techniques are required to verify this checkpoint:
Action Result

1

Verify text and images with color using the following methods.

Pass:

Fail:


©2009 IBM Corporation

Last updated August 25, 2009.