Our Case Studies

Project Name: Bank Portal
Client is a diversified financial services company providing banking, insurance, investments, mortgage and consumer finance for more than 23 million customers reaching through 6,100 stores, the internet and other distribution channels across North America and elsewhere internationally.

The company headquartered in San Francisco, but decentralized so every local store is a headquarters for satisfying all the customers' financial needs and helping them succeed financially. Client has $483 billion in assets and 167,000 total team members across our 80+ businesses. The company is one of the United States' top-40 largest private employers.


Project Overview
Client application provides information related to Individuals, Small Business, Commercial etc. For Individuals, company provides information under the "Banking", "Loans", "Investment & Insurance" and "Self Services" heads. For Small Business, company provides information under the "Banking & Credit", "Business Services", "Resources" and "Self Service" heads. For Commercial, company provides information under the "Online Solutions" and "Business Solutions" heads. The company also provided the On-line transaction facilities to its clients/customers. The company provides enhanced facility to the users by providing On-line account creation, checking and fund transfer facilities. Client required  validation of their website for Section 504, 508 accessibility compatibility
In this project we needed to prepare Use Case Document, Module list and Testing Checklist.

The creation of Use Case document & Testing of is a bit challenging because it involves all the steps require to navigate a webpage for the disabled users and to test/mark various violations that can cause hindrance from accessing the website.

The challenging task was to create the Use-case explaining each step for doing On-line transaction, as these transactions are very risky. Compatibility testing is critical for the client as incompatibility can lead to revenue loss, punitive damages.
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.

Technology Used
  • Manual Testing
  • DEV Partner
  • IE DOM Inspector
  • SnagIt 8

Back to Main