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


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


Summary to be added once test is complete.


The Simple Text Inline Edit 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).


This test should discover:

  • Is the rollover highlight and the tool tip enough for discoverability (or do we need a more permanent visual indicator like a faint outline)?
  • Do users realize fields are editable?
  • Are users successful at editing simple text?
  • Do users understand how edits are saved (clicking outside the field)?
  • Are visual affordances meaningful and helpful to users?
  • Is it obvious to the user that an edit has been made?
  • Do users realize they can undo an edit by clicking on the "Undo" icon?
  • Do users realize they can redo an edit by clicking on the "Redo" icon?

Success Criteria

A successful design has been achieved when:

  • 80% of users realize they can edit inline.
  • 90% of the users that realize they can edit inline can successfully make inline edits.
  • 90% of users that make inline edits recognize whether or not an edit has been successful.
  • 80% of users realize they can undo an edit by clicking on the "Undo" icon
  • 60% of users realize they can redo an undone edit by clicking on the "Redo" icon


Method and test coordinator script.


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 [fluid:Selecting and Recruiting User Test Participants].

Interaction Design

Underlying design patterns and description of component behavior.

Test Environment

Location and version of the environment to be used. Attach a screenshot of the environment at the time of testing if the environment will change over time.


Full notes and analysis of the user tests.

Simple Text Inline Edit User Testing - Round 3 Results