Funded By University of Illinois Library Innovation Fund
Lessons Learned – Usability Testing
Participants
Nick Hoyt
Dena Strong
JaEun Jemma Ku
Discussion Topic
Review/analyze three usability testing sessions – result patterns
UX lunch club idea/feedback regarding UI design
Block format discussion regarding Library requirements
Resolution
Change/improve vague ” remove format” to specific ones such as “remove heading” or “remove style”
Change in tool bar configuration in the second row as the order of
Bold button, Italic button, Inline style menu, remove format button, divider, Special character button, language button (see the attached image below)
Gather info about “review format/normal” from other editors such as google doc, MS word, Box) -> comparative analysis by Dena Strong
Next “lessons learned meeting from the rest of usability testing” will be on the week of August 14, in which all the usability testings are done.
Discussion and Suggestions from Usability testing
Users are confused how to remove “block quotation” style ->redundancy of ” “remove format” function throughout User interface such as “remove format button”, “T” with underline and x mark
“inline style” can become “menu” button” not “richcombo” button in CK source function for the consistency
Feedback to CKsource -> Language menu button is icon only label, which appears to be kanji character, user thinks that the icon
will translate the existing language, not tagging it
will add special characters
Discussed adding “Normal” menu option under “heading” menu. “Normal” menu is the same function as “remove format” under heading menu
Adding font size options such as ” larger” or “smaller” rather than pixel size would help to prevent the users using heading level as a visual style. -> need to confirm its implementation with the rest of group members
Trying to find a way to give users ability to remove specific formats in consistet and intuitive way