Page Comparison

Status

Completed November 2008 by Erin Yu, Allison Bloodworth, Daphne Ogle, & Judy Stern

Summary

Notes

Goals

This test should discover:

• Is the highlight on rollover 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.
• 100% of the users that realize they can edit inline can successfully make inline edits.
• 100% 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

Protocol

Method and test coordinator script.

• Simple Text Inline Edit User Testing - Round 2 Protocol

Users

The desire is to test across a range of technology skill of students and faculty. Users tested in this round are from the University of Toronto, University of California-Berkeley and Unicon.

Interaction Design

Underlying design patterns and description of component behavior.

• Inline Edit
• Inline Edit Design Pattern

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.

• http://build.fluidproject.org/fluid/sample-code/inline-edit/section-info/section-info.html

Results

Full notes and analysis of the user tests.

Simple Text Inline Edit User Testing - Round 2 Results

More...