Testing Protocol

The protocol below describes basic steps you can take to identify and document accessibility features and barriers in new technologies. Not all of these tasks will apply in every scenario, and some technologies may require testing that is not described here. For support with conducting these tests, contact the IT Accessibility Group (itaccessibility@uiowa.edu)

Request and Review Accessibility Documentation from Vendor

Success Indicator: VPAT/other accessibility documentation received and reviewed.

  • Contact vendor and requesting unit representatives
  • Review vendor reply with requesting unit representative

Define Scope

Success Indicator: Testing tasks are identified; list is compiled

  • Become familiar with resource, or recruit a knowledgeable user to assist
  • Identify essential tasks and processes
  • Complete task list, worksheet, or form

Automated Testing (where applicable)

Success Indicator: Application passes violation and warning notifications; manual checks documented

  • Identify automated testing tools (e.g., WAVE, Acrobat Accessibility Checker, Microsoft Office Accessibility Checker)
  • Test individual application views and states with appropriate testing tool
  • Identify Manual Checks for additional manual review as below
  • Validate code for accuracy, completion (SC 4.1.1)

Keyboard Testing

Success Indicator: User can complete tasks independently using only keyboard

  • Identification, focus and activation of any interactive controls (SC 2.1.1)
  • Identify any keyboard traps (SC 2.1.2)
  • Tab/keyboard order follows logical reading order (SC 1.3.2, SC 2.4.3)

Assistive Technology Testing

Success Indicator: User can complete tasks independently using keyboard and screen reader

  • Text alternatives for image or non-text elements (SC 1.1.1)
  • Structure allows user to maintain orientation (SC 1.3.1)
  • Content presents in logical reading order (SC 1.3.2)
  • Identification, focus and activation of any interactive controls (SC 2.1.1)
  • Clear guidance, cues, labeling of interactive components (SC 3.3.2)
  • Error prevention, alerts, and corrections (SC 3.3.4)

Visual Testing

Success Indicator: User can complete tasks independently using visual cues

  • Color is not the only means of distinguishing an object or state (SC 1.4.1)
  • Foreground elements contrast sufficiently with backgrounds (SC 1.4.3)
  • Content can be magnified to 200% without loss of content or functionality (SC 1.4.4)
  • Visual tracking of cursor position (SC 2.4.7)
  • Clear guidance, cues, labeling of interactive components (SC 3.3.2)

Navigability Testing

Success Indicator: User can traverse content with substantially equivalent ease of use

  • User can bypass long or redundant navigation blocks (SC 2.4.1)
  • Tab/keyboard order follows logical reading order (SC 1.3.2, SC 2.4.3)
  • Change of context does not unexpectedly move user out of expected focus position (SC 3.2.2)

Post-Testing Review

  • Compare and contrast automated and manual results
  • Adjust for essential processes, unknowns, intangibles
  • Present results to project team
  • Engage with technology provider on results

EEAAP

Results from this testing protocol should inform an Equally Effective Alternative Access Plan (EEAAP) or similar remediation efforts. Visit the UI’s EEAAP website for more information on developing an Equally Effective Alternative Access Plan. (https://itaccessibility.uiowa.edu/EEAAP)