The process of Web Content Accessibility testing comprises of:
1. Preparation of Use cases: Use cases are prepared to describe the steps of the important processes of the application in such a manner that a disabled person is able to complete the process without any difficulty or failure. Even a small mistake in the description can result in the user ending up on an entirely different page or performing a different action than what was intended.
2. Module list: The Module list contains the screenshots of the screens that appear due to navigation or action performed on the application and the steps of navigation performed to reach the screen. The idea is to select all the screens for testing which have complex page structure and can cause hindrances for the disabled users.
3. Manual and Automatic testing: The modules selected in the “Module list” are manually and with automatic tools against violations as described in the accessibility guidelines related to navigation, keyboard accessibility, simulated controls, data tables, form fields, JavaScript, frames, etc.
4. Preparation of Manual Testing Notes: This document contains the prominent examples of each violation of the accessibility guidelines that were found while manual and automatic testing of the screens of the application selected in Module list.
Selection of Use cases and modules for Module list is of great importance.
We had to make sure that our use cases cover all the key features of the application and that the goal of each use case is successfully achieved by the disabled user.
While selecting the modules for Module list, we try to cover all the screens with complex page structure for testing so that we report all the features which do not follow the accessibility guidelines.
The report is used to either redesign those features or provide the accessibility options to disabled users for accessing those features.