Skip to main content

Visual cue for audio alerts

Java™ checkpoint 3.1

Rationale

Techniques

Testing

 

Rationale

Users may not be able to hear or distinguish sounds if they are deaf or hard-of-hearing, work in noisy environments, or turn off sounds to avoid disturbing others. In order for these users to respond to audio alerts, those alerts must be presented visually as well. Typical alerts might be the receipt of new mail, beeps to indicate system errors, or sounds to indicate a change in status.

Back to top

Development techniques

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

  • Respond to system settings by using JNI to call an operating system specific resource (e.g. Window's dynamic link library - DLL or UNIX system object - SO) that responds to the system setting that supports visual cues for system audio alerts (beeps). For example, on Windows WIN_ALARM and WIN_BEEP respect the SoundSentry setting in the Control Panel - Accessibility - Sound settings.
  • Provide an option for users to display visual cues for audio alerts. Examples of visual cues include:
    • Display a status indicator in the notification area of the taskbar that flashes when initially displayed to attract the user's attention.
    • Display a text message in a message dialog using javax.swing.JOptionPane.
    • Display a message in a dialog using javax.swing.JDialog.

Back to top


Testing techniques

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

Tools

There are no tools required to test this checkpoint

Windows techniques

The following techniques are required to verify this checkpoint:

  Action Result
1 Test with SoundSentry enabled to verify there are visual cues for system audio alerts.

  1. Goto Control Panel - Accessibility Options. On the Sound page, select the option to "Use SoundSentry".
  2. Switch focus back to the application software.
  3. Perform an action that causes the software to generate a system audio alert.
  4. Verify that the software provides a visual cue for system audio alerts.
 Pass:

The software provides visual cues for system audio alerts. The following visual cues may be used:
  • A message box for the alert.
  • A status indicator on the notification area of the taskbar that flashes when initially displayed to attract the user's attention.
  • A text message in a status window.
  • A dialog.

Fail:

There are no visual indications for the system audio alerts. If there are no cues using ShowSounds, perform the next test to see if there is an application option to display visual cues.
2 Test the user option to display visual cues for audio alerts. You do not need to perform this test if the SoundSentry test was successful.

If the software did not provide a visual cue with SoundSentry enabled, it must provide a user option to show audio alerts visually.
  1. Enable the user option to display visual cues for audio alerts
  2. Perform an action that causes the software to generate a sound
  3. Verify that the software provides a visual cue in addition to the audio alert.
 Pass:

The software provides visual cues for audio alerts. The following list provides examples of visual cues that may be used:
  • A message box for the alert.
  • A status indicator on the notification area of the taskbar that flashes when initially displayed to attract the user's attention.
  • A text message in a status window.
  • A dialog.


Fail:

  • SoundSentry did not enable visual cues and there is no user option to enable visual cues for audio alerts
  • The application provides a user option to enable visual cues, but the visual cues were not displayed

Back to top


©2001, 2008 IBM Corporation

Last updated February 15, 2008.

Previous

Checklist

Next