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

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.


Required development techniques


The following techniques are the minimum required to meet Checkpoint 2.4 from the IBM Software Accessibility Checklist:

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

Examples of required techniques

1. Provide keyboard equivalents for all actions.

Example 1

Refer to Software checkpoint 1.1 keyboard equivalents for information required to support this technique.

2. Provide a visual focus indicator that moves among interactive objects as the input focus changes. The focus must be programmatically exposed to assistive technology.

Example 2

Refer to Software checkpoint 2.1 visual focus indicator for information required to support this technique.

3. Provide semantic information about user interface objects.

Example 3

Refer to Software checkpoint 2.2 object information for information required to support this technique.

4. Associate labels with controls, objects, icons and images.

Example 4

Refer to Software checkpoint 2.3 labels for information required to support this technique.

5. Provide text through standard system function calls or through an API which supports interaction with assistive technology.

Example 5

Refer to Software checkpoint 4.1 text for information required to support this technique.

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

Example 6

Refer to Software checkpoint 4.2 color for information required to support this technique.

7. Provide an option to adjust the response times on timed instructions, or allow the instructions to persist.

Example 7

Refer to Software checkpoint 5.1 response times for information required to support this technique.


Required test techniques

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

Test techniques

Use the required test techniques from the following checkpoints to verify this checkpoint:


Action Result

1

Test keyboard navigation using the required test techniques for checkpoint 1.1 - keyboard equivalents.

Use the pass/fail criteria defined in checkpoint 1.1.

2

Test visual focus using the required test techniques for checkpoint 2.1 - visual focus indicator.

Use the pass/fail criteria defined in checkpoint 2.1.

3

Verify that semantic information is provided for objects using the required test techniques for checkpoint 2.2 - object information.

Use the pass/fail criteria defined in checkpoint 2.2.

4

Verify that labels are associated with controls, objects, icons, and images using the required test techniques for checkpoint 2.3 - labels.

Use the pass/fail criteria defined in checkpoint 2.3.

5

Test text using the required test techniques for checkpoint 4.1 - text.

Use the pass/fail criteria defined in checkpoint 4.1.

6

Verify that color is used only as an enhancement using the required test techniques for checkpoint 4.2 - color.

Use the pass/fail criteria defined in checkpoint 4.2.

7

Test all timed responses using the required test techniques for checkpoint 5.1 - response times.

Use the pass/fail criteria defined in checkpoint 5.1.

8

All of the above test steps must be completed for every electronic form in the application before you can determine whether this checkpoint passes or fails.

Pass:

Fail:


©2009, 2013 IBM Corporation

Last updated October 5, 2009.