[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    [Kde-usability] Summary of icon test
From:       Jono Bacon <f9808590 () wlv ! ac ! uk>
Date:       2001-03-24 16:41:20
[Download RAW message or body]

Hello all,

After some interesting discussion on kde-look and kde-usability, I have 
summarised the main points we need to consider in taking the test. These 
pretty much line up with my opinion and HCI research I have done.

 - Timing candidates for response time to a question is a difficult thing to 
do, and really does'nt provide us with much usable data. This is due to 
people multitasking and watching babylon 5. ;-)

 - We need to provide icons withing context. This has caused mixed 
discussion, but I feel we should provide all icons within a certain context. 
This is because humans work context sensetively, and icons also work context 
sensitively. Some icons however are not context sensitive (such as formatting 
commands; bold, italic etc). We should first provide general non-context 
icons and then provide icons within applicatio domains such as Word 
Processor, Spreadsheet etc.

 - For each ico, the user should indicate their level of challenge in 
identifying the icon. This can be a combo box with: Easy, Not so easy, 
Challenging, Difficult, Guess etc.

 - We need to be careful not to overwhelm the user with questions. Initially 
the plan was to put all the icons on a single page. This is something we need 
to resolve.

 - The page will be based ona website for accessability. We will be accessing 
users via a website, and not through specialist meetings such as LUG meetings 
and trade shows. The aim is to get someone who can do the test, and get 
people who would not be familier to do the test.

 - At the top of the page we will take some personal data such as Age, 
Country, Gender etc to build a profile of the user. We will also gather data 
on their experience of usin computers and other systems.

The main things we need to consider in questionnaire design are:

 - The language of the questions - how we structure the queston so the user 
understands it

 - Support - if the user can get help if they dont understand the question

 - Context - how is the user taking the test? Is it rushed?

 - Integrity - we need to try and make the tests as valid as possible. There 
is always gona be a margin of error (particularly remote testing such as web 
tests), but we need to do our best to limit bad data.

Also...could everyone try to keep discussion on kde-usability as much as 
possible. It is just a bit confusing tracking two threads on here and o 
kde-look. :-)

	Jono 

-- 
Jono Bacon - [vmlinuz] - jono@kde.org
KDE/Qt Developer
_______________________________________________
kde-usability mailing list
kde-usability@master.kde.org
http://master.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]