Friday, May 11 - 8am PDT / 10am MDT / 11am EDT / 4pm GMT
Breeze: http://breeze.yorku.ca/fluidwork/Image Added
* Introductions / interest in heuristic work
* Update from Clayton on accessibility heuristics research
* Review/thoughts on material shared so far
* Discuss heuristic checklists
* Discuss evaluation protocol / format (straw man)
* Need volunteer evaluators
o same evaluator for usability and accessibility?
* Identify leads for Sakai, Moodle, uPortal heuristics (some thoughts on responsibilities):
o Coordinate / create activity list for each project
o Split evaluation into reasonable chunks (2 - 3 hours for each evaluator)
o Coordinate review
o Coordinate synthesis of findings, prioritization & recommended solutions
o Coordinate/write report for communities
"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?
Heuristic checklists to ponder