Another interesting presentation I attended was from Dr Danial Woo – University of New South Wales.

This session presented the outcomes of Moodle usability evaluation sessions using the eye-tracking software. The sessions were to determine ease of process and use of Moodle and a teaching and learning tool.

This software showed us (via Infrared) exactly where teachers were looking for information and buttons to click when creating a course in Moodle.  This provided me with a valuable insight into how teachers use Moodle and gave us some ideas on how we can incorporate the results into our own training at NCTAFE.

Moodle usability evaluation session

The Moodle founders and developers were also present in this session and keen to collaborate about some of the user results, some of which are listed below.

• Tendency to focus on the big blue headings in the middle of the screen, which didn’t look click-able, wandering eyes indicated confusion as to where to go next, so user became engaged with the search box
• Users unaware that they were logged in
• Much confusion for teachers on the course setting page about what ‘Roles’ are
• After course creation, you are directed to assign people to a ‘role’. Once you do this, there is no submit or ok button, so users get confused, finally realising they need to use the breadcrumb links to go back to the course
• The link to/attach files dialogue is confusing, where does it actually upload the files? Note: this feature will be improved in the new version
• Limited to choosing one file at a time to upload
• Some confusion about how to add participants to a course
• No explanation of adding a hidden ‘teacher’ when you Assign Roles
• Some confusion of the editing icons, e.g. indenting a resource icon not that clear

There were also some great tips for Usability Testing;

• Use a quiet space to conduct usability testing
• To create true user-centered design, work with your users, get them involved early (it expensive to make the changes later)
• test early, test often (this will result in cost saving)
• Start designs on paper
• Treat it like a science experiment
• Start simple and then build on your course
• Don’t give instructions to users by using the exact language e.g. “click this button”. Give users a more generic goal, e.g. “Here are some files, upload them to the course”
• Track trends, not just one lot of results
• Analyze findings and create solutions
• Use a note taker, don’t be distracted by taking notes yourself
• Check out the Apple Human Interface Guidelines

What are the implications of this testing?

• Develop Moodle – we can all contribute to the Moodle community. Vote for issues that as teachers, we would like to see fixed first (you can do that here).
• Train more effectively, incorporate these issues into our training
• Continuous Improvement results in happier users, increased performance