Accessibility (ATV)

In accordance with section 508 of the Rehabilitation Act of 1973, BMC Software is committed to making its products and services easier to use for everyone including people with disabilities.

Performance Test is a mainframe application that runs on IBM’s z/OS operating systems. It has an ISPF interface that is accessed with IBM 327x-type terminals or with 3270 terminal emulator software. Since the mainframe environment offers few accessibility features, We focus our attention, with regard to accessibility, on 3270 terminal emulator software running on personal computers (PCs) with Microsoft Windows 2000 or more current. Performance Test supports, with a few exceptions, Microsoft Windows accessibility features and Window-based Assistive Technology (AT) software and devices, such as Braille devices, screen readers, magnifiers, etc.

Important

Performance Test is intended for use by mainframe software developers, programmers, and testers. Much of the input and output used or produced by Performance Test, such as Job Control Language (JCL) and hexadecimal contents or dumps of memory, are not easily understood by the general public. Unfortunately, as in the case of hexadecimal dumps, data in these formats can be confusing to screen readers and therefore confusing to the people who use them. Effective use of this application requires the specialized knowledge of a mainframe systems software developer or programmer.

Performance Test accessibility was evaluated using:

  • Freedom Scientifics’ JAWS screen reader
  • Attachmate Corporation’s myExtra Presentation Services tn3270 emulator
  • Microsoft’s Windows accessibility features
  • Adobe Reader using the “Read Out Loud” function.

This evaluation not only identified accessibility exceptions, but revealed emulator and screen reader compatibility issues that in some cases can be remedied through appropriate configuration.

Installing Windows accessibility features

Microsoft Windows operating systems offer several accessibility features to aid individuals who have difficulty typing or using a mouse, who are blind or have low vision, or who are deaf or are hard-of-hearing. Install these features during setup or later using the Windows installation disks. See to the “accessibility” topics in the Windows Help system for information on installing and using these features. Visit the Microsoft Web site, http://www.microsoft.com/enable, for additional information and tutorials.

Selecting font and font size

Microsoft Windows and emulator software packages offer font and font size settings to accommodate users with low vision. The emulator software’s tool bars and dialog boxes typically use the font specified in the operating system, while the terminal presentation uses the font and font size specified in the emulator. To change the font or font size:

  • Presented on the toolbars and dialog boxes, see to the Windows Help system.
  • Presented in the terminal window, see to the emulator’s documentation or Help.

Some screen readers recommend certain fonts and font sizes for compatibility. For example, Freedom Scientifics recommends setting the font to a common or “plain” font such as Lucida, Courier, or Times New Roman, and setting the font size to 10 points or smaller. See to the screen reader’s documentation or Help for these recommendations.

Changing color and contrast

Color and contrast settings can assist users with low vision. ISPF and most emulator software packages offer color and contrast settings. If you are accessing Performance Test with a terminal, use ISPF settings. Otherwise, adjust the color and contrast in the emulator software. See to ISPF Help or the emulator’s documentation or Help.

Setting cursor blink rate

The blink rate of the cursor can affect users with photosensitive epilepsy. Additionally, some screen readers require a specific blink rate. Some readers automatically adjust the blink rate while others expect you to adjust the rate. Refer to:

  • The Microsoft Windows Help to find out how to set the cursor blink rate.
  • The screen reader’s documentation or Help to find out the recommended blink rate.

Using keyboard shortcuts

Keyboard access to application functions support users who cannot use a mouse.

Microsoft Windows provides keyboard access to all functions within the operating system, such as:

  • Displaying or hiding the Windows Start Menu
  • Showing the Desktop
  • Minimizing all windows
  • Searching for files
  • Accessing the help system
  • Controlling the behavior of the Windows accessibility features, for example, toggling the listening status to the microphone, or cycling focus backward and forward.

Most Windows-based applications also provide keyboard access to their functions. The combination of keys required to execute a given function is called a keyboard shortcut. See to the “Keyboard Shortcuts” topics in the Windows Help system for a complete list of Windows shortcuts. For a list of the shortcuts that are available in the emulator software or any third-party accessibility tool, such as the JAWS screen reader, see to the software’s documentation or Help.

Accessibility exceptions work arounds

During Performance Test accessibility evaluation, some exceptions were encountered where some accessibility features or AT were not fully supported. The causes of and solutions for these exceptions are currently under investigation by BMC Software.

Known exceptions

Accessibility exceptions include:

  • Function Key (F Key) information at the bottom of the screen is not read by the screen reader on some screens. This is believed to be caused by an external interface. See Solutions section for a viable work-around.
  • Some system error and warning messages are not read by the screen reader when issued. Believed to be caused by an external interface. See Solutions section for a viable work-around.
  • Some pop-up dialog boxes or windows do not capture exclusive focus and are not read correctly by the screen reader. This is believed to be caused by an external interface. No known solution is currently available.
  • System error and warning messages do not capture visual focus for the screen magnifier. This is believed to be caused by an external interface. No known solution is currently available.
  • Some entry and display fields lack individual labels. When entry fields are accessed using the Tab key, the entire individual line is read.
  • Current Web-based reports are not easily navigated using the keyboard and lack table element coordinate tags. Additionally, some of these reports contain color-coded elements — for example, the color of some elements conveys meaning.

Solutions

When the screen reader fails to read the F Key information upon entry to a new screen, do one of the following:

  • Use the arrow keys to move the cursor down to the lines with the F Key information. The screen reader reads each line as the cursor is placed on it.
  • Press the Page Up key for the screen reader to reread the entire screen.

When the screen reader fails to read an error or warning message, an audio alert occurs if this feature is enabled on your system. Press the Up key to place the cursor on the line containing the error message, usually on the top or title line. The screen reader reads the line and its error message individually.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*