User Experience Walkthrough Report
...
Section |
---|
Column |
---|
| This page presents a template for reporting the results of a UX Walkthrough which can be used with any website or software product. Examples of product-specific templates with details of how they were used by the Fluid teams may be found at Sakai User Experience Walkthrough Report and uPortal User Experience Walkthrough Report Generic UX Walkthrough Report TemplateThis template covers accessibility and usability heuristic evaluations combined with cognitive walkthroughs |
|
...
. Evaluation Completed by: [Insert |
|
...
evaluator's name] URL: http://.... [Insert URL of the test site] Date: [Insert Date and time the evaluation was performed] Heuristic reviews and cognitive walkthroughs were performed on a [computer type] |
|
...
at [screen resolution] resolution (most common resolution) and [color setting] colors (most common novice resolution; if graphics work at this resolution, they'll work in higher resolutions) using [Browser and Operating System] at a [type of connection is internet required] connection rate. See |
|
...
...
heuristics used in this evaluation. Scope of Walkthrough• Functional Areas focused on for review
User profile(s) and context of use:Profiles will generally only be used for the cognitive walk-through, not the heuristic evaluation. However, users may be set up with a certain role in the system (e.g. student, instructor) for the heuristic evaluation. • User Profiles or Personas |
|
...
ScenariosScenarios will generally only be used for the cognitive walk-through, not the heuristic evaluation. However, it is fine to use these scenarios for the heuristic evaluation if it is helpful to evaluators in figuring out how to walk through the application. • General Overview ( |
|
...
heuristic evaluation) • Finding..... • Scenario 3 • Scenario 4 • Scenario 5 Assumptions for this evaluation:• [List any additional assumptions used in evaluation] Positive FindingsAll positive findings, from both the heuristic evaluation and the cognitive walk-through, should be placed in this section. Usability Positives | Tool | Evaluator |
---|
| | | | | | | | | | | | | | | | | | | | | | | | | | | Accessibility Positives | Tool | Evaluator |
---|
| | | | | | | | | | | | | | | | | | | | | | | | | | |
Summary of Usability & Accessibility Issues Found All usability & accessibility issues found, in both the heuristic evaluation and the cognitive walk-through, should be placed in this section. Priority Legend: High = Task cannot be completed Medium = Task completed with significant effort and failed attempts Low = Task completed with minor complications and/or annoyance |
|
Summary of Issues Found
...
Usability Issues | Principle | Link to screen shots | Priority | Suggestions for solution |
---|
|
|
...
| Tool | Component Identified?
|
---|
| | | | | | | | | |
|
|
...
...
...
Accessibility Issue | Principle | Link to screen shot
| Priority | Suggestions for solution | Tool | Component identified?
|
---|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
|
Adaptive Technology (AT) Review Form Worksheet
...
Question
...
Yes/No
...
Problem(s)
...
Desired Behavior(s)
...
Recommended Repair(s)
...
Priority
...
...
Cognitive Walkthrough WorksheetThis section should be used by evaluators to keep track of the steps & screens they followed through the application in the cognitive walk-through. Any positive results or issues found should be included in the two sections above. Scenario 1: Brief description # | Step | Screen | Comments/issues | Principle | Suggestions for solution |
---|
| | | | |
|
|
...
...
...
#
...
Step
...
Screen
...
Cognitive Walkthrough Worksheet
(issues should be included in summary above)
Scenario 1: Brief description
Scenario 2: Brief description
# | Step | Screen | Comments/issues | Principle | Suggestions for solution |
---|
| | | | | | | | | | |
|
|
...
#
...
Step
...
Screen
...
Scenario 3: Brief description
# | Step | Screen | Comments/issues | Principle | Suggestions for solution |
---|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Scenario 4: Brief description
# | Step | Screen | Comments/issues | Principle | Suggestions for solution |
---|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
Column |
---|
| Panel |
---|
borderColor | #321137 |
---|
bgColor | #fff |
---|
titleBGColor | #c1b7c3 |
---|
borderStyle | solid |
---|
title | Related Links |
---|
| |
|
|