Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

"To Do" list for creating Heuristic Review Protocol

  1. Create list of usabilty accessibility heuristics (based on recognized principles)
  2. Agree on evaluation/reporting format
  3. Work within "application team" to: 
    1. Agree on user profiles
    2. Break apps into chunks
    3. Create usage scenarios for focus

Evaluation Process (draft)

Assumptions:  Protocol has been created

  1. Individual evaluation by 3 - 5 evaluators
  2. Synthesize and prioritize findings
  3. Brainstorm design session (identify conceptual solutions to high priority issues)
  4. Write and share out report
  5. Incorporate findings into community (some will drive component development - others can be used for general product development in the communities)
    1. Sakai - Integrate into requirements group.  Do we need to create jira tickets?  Are these really "design bugs" conceptually and thus have a different status than requirements?
    2. Moodle - how does this get fed back into the process?
    3. uPortal - how do we integrate into their requirements process?  Deliver findings to the community?
  6. Look for pain across applications? Are there issues a component(s) can address well?

 User Experience Inspection

Checklists to ponder:

Heuristic Evaluation Report Example

Usability Heuristic checklists

Accessibility Heuristic checklists

Reference material:

Jacob Nielsen'sdescription and overview

Applying Heuristics to Perform a Rigorous Accessibility Inspection in a Commercial Context 

Usability.gov

Section

...

Upcoming Meeting

Friday, May 11 - 8am PDT / 10am MDT / 11am EDT / 4pm GMT

Breeze: http://breeze.yorku.ca/fluidwork/

Previous meeting notes:   2007- May - 11 Meeting Agenda and Notes

borderfalse
Column
width70%

What are Fluid UX Walkthroughs?

Excerpt

Fluid UX Walkthroughs are a combination of usability and accessibility reviews of Fluid partner applications, with the goal of identifying user "pain points," and then proposing and prioritizing user interface improvements to address them. Read more about UX Walkthroughs

Evaluations are conducted as:

  • heuristic evaluations - comparing the user interface against an accepted set of "rules" or heuristics.
  • cognitive walkthroughs - determining how easy it is for a user to use the application.
  • Code convention compliance reviews - evaluating compliance to a set of best practices for achieving accessibility and usability.

How are Fluid UX Walkthroughs Performed?

Fluid UX Walkthroughs are performed by reviewers with diverse areas of expertise residing at a number of different institutions. To ensure consistency of approach and results the following material has been created to guide their efforts.

The protocols and guidelines will continue to be refined as we learn from doing the hybrid inspections/evaluations.

Fluid Project Walkthroughs and Working Groups

Within the Fluid Project, walkthroughs have been performed by walkthrough working groups. Most of the groups have had representatives from two or more institutions, with each group focused on a specific product.
Products examined so far include uPortal, Sakai, and Moodle.

Results from Previous Walkthroughs

UX Walkthrough Results:

Excerpt Include
UX Walkthrough Results
UX Walkthrough Results
nopaneltrue

UX Walkthrough Project Plan

Excerpt Include
UX Walkthrough Project Plan
UX Walkthrough Project Plan
nopaneltrue

> Learn more

Column
width30%
Panel
borderColor#93BB6F
bgColor#F8F8F8
titleBGColor#D3E3C4
borderStylesolid
titleOn this Page
Table of Contents
minLevel2
Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
borderStylesolid
titleRelated Links