Fantastic article. It’s so important to know what you are testing. It’s easy to be distracted from that. With “low res” mock-ups (paper prototypes, etc), it’s easy to make hundreds of variations for each step of the process… You’re generally not testing their ability to click a form widget, but you are probably testing their ability to navigate a new site based on an established workflow. The main versions of the screens are all you should need to conduct that study. A/B testing is also a good idea, especially if you’re asking your audience to change their workflow.

Let me put a scenario to you – I am developing a Moodle unit for a University course. I am using the unit to support a face to face element of a blended learning experience.

Given that I am not very technically literate, my main interests – apart from the content – are the text, font and layout, as well as the use of graphics and assessment resources (ie how do I find out what they know).

What are five major issues involved in assessing the usability of a site, and what references to WCAG 2.00 would be required? Also how given that I am time poor, what is minimum number of participants required to complete this test/