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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Current »

Status

Planned March/April:  Accessibility testing at Landmark College and 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:

  • Do users realize they can move portlets?
  • Are users successful at moving portlets around the portal?
  • Can a user move a portlet successfully to a chosen location?
  • Do users recognize and understand locked vs. unlocked portlets?

Success Criteria

A successful design has been achieved when:

  • 75% of users realize they can move portlets after exploring the interface.
  • 50% of users realize immediately they can move portlets.
  • 75% of users can successfully drag a portlet to a chosen location and drop it.
  • 75% of users can differentiate between locked and unlocked portlets and understand that they cannot move locked portlets.

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 was used. Attach a screenshot of the environment at the time of testing if the environment will change over time.

Results

Full notes and analysis of the user tests.

Layout Reoderer User Testing - Round 4 Results

TBD

More...

MORE ON USER TESTING
Recent updates

There are no recent updates at this time.

MORE ON LAYOUT CUSTOMIZER
Recent updates

There are no recent updates at this time.

  • No labels