Access-IT California Getting Started Project Planning and Analysis Active Projects Existing Systems Resources And Tools


Within the testing phase of an IT project, the business analyst, application developer and system tester are critical to success. The criticality of these roles is amplified when conducting accessibility testing, as oftentimes post implementation fixes in these areas are cumbersome or simply not prioritized.

The systems analyst is an architect and plays several roles within the system development life cycle. The analyst is responsible for gathering and documenting systems requirements, including both technical, usability, and accessibility specific items. During the testing phase of a project, the analyst is responsible for:

  • Building and maintaining an accessibility testing into the systems test plan. In this effort, the analyst must ensure that all accessibility-related requirements are incorporated into the plan.

  • Being familiar with accessibility best practices for both development and testing resources.

The application developer, like the systems analyst, is responsible for operating in several phases of the systems development life cycle. Within the testing phase of the project, the developer must:

  • Primarily understand what assistive technology tools are available within the overall marketplace and what specific assistive tools will be used to interact with the production system.

  • Develop a deep understanding of accessibility-related requirements for all phases of SDLC, but specifically in terms of unit testing, validation and verification techniques.

  • Respond to and remediate defects found within the application that are specifically related to accessibility.

The systems tester is the primary resource responsible for the testing phase of SDLC. Within this phase, the system tester must:

  • Be familiar with accessibility standards and requirements. This familiarity must span multiple technologies including web forms, PDF documents, streaming media and mobile applications.

  • Be proficient in the use of common assistive technologies, including screen readers and magnifiers and voice recognition products.

  • Ensure test scripts are generated and test all functional and performance requirements in conjunction with accessibility requirements. This is typically completed by executing tests with either assistive technologies or automated tools.

  • Be familiar with and employ in-browser accessibility testing tools, such as WAVE.

  • Ensure that accessibility issues are documented using the same methods used to document all defects found within the testing phase.


Design | Build | Test | Implement




What to do

How to do it

Follow same standards as outlined for the Analysts above.

Please see above previous section and conduct unit testing consistent with WCAG 2.0.

Have significant knowledge in various assistive technologies and how used by users to consume content on a system or site.

Assistive Technology (AT) generally falls into two categories:

  • AT device any item that directly assists an individual with a disability to increase, maintain, or improve their capabilities.

  • AT service any service such as evaluation of work site, interpreting services, creating OCR (optical character recognition) documentation, and training on assistive technology. Any service that directly assists an individual with a disability in the selection, acquisition, or use of an assistive technology device.

Some examples of assistive technologies include:

  • Screen Readers
  • Magnification Tools
  • Voice Recognition
  • Video Conferencing