"To Do" list for creating Heuristic Review Protocol
- Create list of usabilty accessibility heuristics (based on recognized principles)
- Agree on evaluation/reporting format
- Work within "application team" to:
- Agree on user profiles
- Break apps into chunks
- Create usage scenarios for focus
Evaluation Process (draft)
Assumptions: Protocol has been created
- Individual evaluation by 3 - 5 evaluators
- Synthesize and prioritize findings
- Brainstorm design session (identify conceptual solutions to high priority issues)
- Write and share out report
- Incorporate findings into community (some will drive component development - others can be used for general product development in the communities)
- 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?
- Moodle - how does this get fed back into the process?
- uPortal - how do we integrate into their requirements process? Deliver findings to the community?
- Look for pain across applications? Are there issues a component(s) can address well?
Checklists to ponder:
Heuristic Evaluation Report Example
Usability Heuristic checklists
Accessibility Heuristic checklists
Jacob Nielsen'sdescription and overview
Applying Heuristics to Perform a Rigorous Accessibility Inspection in a Commercial Context