Skip to Main Content
Return to Navigation

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 compliance of 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 features is different from the HTML code that is generated for users who do not enable the accessibility features. Therefore, you must test for accessibility in all of the available accessibility modes:

Note: Testing for accessibility with the accessibility features turned off does not work for screen readers because most accessibility features are available only in Accessible Layout mode. Although Accessible Layout mode 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 Section 508 accessibility standards.

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