Documentation for a historical release of Infusion: 1.3
Please view the Infusion Documentation site for the latest documentation.
If you're looking for Fluid Project coordination, design, communication, etc, try the Fluid Project Wiki.

Skip to end of metadata
Go to start of metadata

Status

Planned for March/April 2009 Accessibility Testing by Landmark College & ATRC

Summary

High-level summary to be added after testing has been completed.

Notes

The Uploader will be used by a wide cross-section of students and faculty in higher educational institutions.

This round of testing will mostly focus on users who use assistive technologies (i.e. keyboard-only users, screen reader users).

Goals

This test should discover:

  • Does the user realize they can upload multiple files?
  • Is the user successful at selecting and adding multiple files?
  • Can the user stop the upload?
  • Can the user remove unwanted files from the queue?
  • Can the user add additional files to upload?
  • Is it obvious to the users whether the files are successfully uploaded?

Success Criteria

A successful design has been achieved when:

  • 100% of users realize they can upload files.
  • 90% of users realize they can upload multiple files.
  • 80% of users can stop.
  • 80% of users can add more files to upload.
  • 90% of users can remove files from the list.
  • 90% of users can successfully upload files and know when they are uploaded.
  • 90% of users recognize where the uploaded files are placed.

Protocol

Method and test coordinator script.

Users

The goal is to test across a range of users in higher education.  We want to get feedback from a variety of roles, experience levels, time and level in school, institutions, etc.  For more on choosing and recruiting users for testing see Selecting and Recruiting User Test Participants.

How many users to test? Neilson suggests that testing 5 users, with a minimum of 3 from each user group, within an iterative design process should be sufficient to find most usability issues.

Interaction Design

Underlying design patterns and description of component behavior.

Test Environment

Location and version of the environment that is used.

NOTE:  Attach a screenshot of the environment at the time of testing if the environment will change over time.

Uploader Example on build.fluidproject.org (Server connected example)

Uploader User Testing - Round 4 Results

To be completed after testing

More...