Skip to main content

Forms

Java™ checkpoint 2.5

When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements and functionality required for completion and submission of the form, including all directions and cues.

Rationale

Techniques

Testing

 

Rationale

Electronic forms are used by many software programs to gather information from users such as those used for online product registration and updates. The accessibility of the electronic form depends on proper coding of the controls so the information is exposed to screen readers.

Back to top

Development techniques

The following techniques are the minimum required to meet Checkpoint 2.5 from the IBM Java Accessibility Checklist:

  • Provide keyboard equivalents for all actions.
  • Provide a visual focus indicator that moves among interactive objects as the input focus changes. The focus must be programmatically exposed to assistive technology.
  • Provide semantic information about user interface objects.
  • Associate labels with controls, objects, icons and images.
  • Provide text through standard system function calls or through an API which supports interaction with assistive technology.
  • Use color as an enhancement, not as the only way to convey information or indicate an action.
  • Provide an option to adjust the response times on timed instructions, or allow the instructions to persist.

Back to top


Testing techniques

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

Tools

Install the following tools to test this checkpoint:

  • A screen reader that supports Java, and the Java Access Bridge (link resides outside of ibm.com)
  • One of the Java testing tools such as JavaFerret (link resides outside of ibm.com) from Sun.

Windows techniques

The following techniques are required to verify this checkpoint:

  Action Result
1 Test with a screen reader and verify all information on the form is spoken.
  • Navigate to each input field using the keyboard with the screen reader to read:
    • Text labels
    • Object type (role) (e.g. radio button, checkbox, edit field)
    • Object status if appropriate (e.g. a radio button or checkbox that is checked)
    • Object contents (e.g. default text, combobox content)
  • Static text that is not an input label (e.g. instructions at the top of the form) will not get keyboard focus. Consult your screen reader's documentation to see how to read static text in this situation.
 Pass:

The screen reader reads all information on the form including images, static text, text labels, and control information (type, state and content).

Fail:

The screen reader does not read all information on the form.
2 If the screen reader did not read all information on the form, run JavaFerret to see if this is a problem with the application or the screen reader. Use JavaFerret to check specific controls that were not read by the screen reader.
  • Tab to the object or move the mouse over the object that was not read.
  • Verify that JavaFerret displays the appropriate information in the Name, Role, State and Value fields.
Pass:

javaFerret displays information in the following fields:
  • Name: Text label for input field, text on button or tab, alt text for image
  • State: Checkboxes / radio buttons display "checked" if selected, otherwise "selectable", may be "selected" or "focusable" for images, buttons,
  • Role: Type of object (e.g. text, radio button, combo box). Cannot be null
  • Value: URL for a link, default text in an edit field, selected item in a combo box. Value may be null for push buttons, checkboxes, radio buttons or blank edit fields.

Fail:

JavaFerret displays null or incorrect information in the following fields:
  • Name: Text label displayed as "none" or null even when visible on screen
  • State: Selected checkboxes / radio buttons display "focusable"or selectable" instead of "checked"
  • Role: Null or none. All objects must have a role.
  • Value: Null or none for items in lists, combo boxes or default text in edit fields
3 If the application uses color, print a copy of the screen in black and white or visually inspect the screen 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.
example using color to identify required fields

Back to top


©2001, 2008 IBM Corporation

Last updated February 15, 2008.

Previous

Checklist

Next