Testing for Accessibility

When testing for accessibility, it's important to include a wide variety of users with various disabilities, test various assistive technologies, and include a combination of manual testing (for example, with the keyboard) and automated testing using scripts or browser add-ons to verify the HTML code. Various web resources and books are available outside of Oracle to help you develop your testing plan.

In addition, the HTML code that is generated for users who enable accessibility layout features is different from the HTML code that is generated for users who do not enable the features. Therefore, you must test for accessibility in all of the available accessibility modes:

  • Test when the Accessibility Layout option is set to Screen Reader On with various assistive technology, such as screen readers.

    If possible, test with users who are familiar with how the assistive technology works.

  • Test keyboard navigation with accessibility layout features turned off.

    Many accessibility users do not have vision problems, but they still use the keyboard instead of a mouse due to physical discomfort or disabilities.

Note: Testing for accessibility when the Accessibility Layout option is set to Screen Reader Off does not work for screen readers because most accessibility layout features are available only in Screen Reader On mode. Although when the Accessibility Layoutoption is set to Screen Reader On may be more difficult to navigate for sighted users, you must use it to test with screen readers.

To determine the full list of features that you need to test, review the WCAG 2.0 Level A and AA standards.

The following list provides a high-level overview of the accessibility layout features that you should test after customizing applications in PeopleSoft Application Designer:

  • Can users complete tasks using only the keyboard?

    • Is the tab order correct?

    • Are keyboard shortcuts assigned to page tabs and grid tabs?

  • Do screen readers track the on-screen focus?

    • Do pages use the Deferred processing mode?

    • If pages do not use Deferred processing, is field processing minimized?

  • Do all functional images and user interface elements have meaningful, unique labels?

    • Do functional images (static, dynamic, and button) have labels?

    • Do data entry fields have labels?

    • Do push buttons and hyperlinks have labels?

    • Do grid columns have labels?

    • Do grids and scroll areas have titles?

    • Do grids have summaries?

    • Are labels deactivated for decorative images?

  • Are images used consistently?

  • Do foreground and background colors provide sufficient contrast?

  • Do pages provide alternatives to color coding to convey meaning?

  • Do pages contain links to skip repetitive navigation?

  • Is HTML that is not generated by PeopleTools (such as code in an HTML area) or an applet coded to the WCAG 2.0 AA accessibility standards?