- From: Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com>
- Date: Fri, 10 Aug 2007 16:05:35 -0400
- To: rachna.w3c@gmail.com
- Cc: "W3 Work Group" <public-wsc-wg@w3.org>
- Message-ID: <OFA7062258.1D13FC7B-ON85257333.006457CF-85257333.006E7184@LocalDomain>
In PII Editor Bar:
"We require a prototype implementation of this proposal to do further
analysis, because much of the usability and security will depend on
specific design decisions. "
I find that worrying from a standardizing perspective. If the specific
design decisions cannot be cannonicalized in conformance language (which
doesn't necessarily follow, but seems to be a potential given what you
say), then much of the usability and security would not be part of the
standard per se.
In Page Security Score:
"There are a number of interesting things to test here, which can be
studied very easily using low-fidelity prototyping methods"
Would it make sense to pull in Audian on this? He has a lot of hands on
experience doing that for products.
"Users are habituated to clicking yes to dialog boxes regarding security.
They will not read the dialog, and instead find a way of dismissing and
continuing on to their primary task "
Some will, and some won't. In one "in the wild" study, over half chose
expediency over security. It is in some ways a "best case" scenario for
training and context (work). See:
http://www.acsa-admin.org/2002/papers/7.pdf
Favicons and friends:
I buy that there are similiarities, but couldn't see how the testing would
impact the favicon proposals. Can you say a bit more about that?
On SBM:
"Note on testing: Before continuing with a usability evaluation a design
for the SBM mode interface is necessary. The process for adding and
removing sites on the whitelist needs to be outlined. "
Dan, you're the likely candidate for this. Will you do this? UseEval
folks, how do you want to track things like this? As (requested) actions,
or as issues?
At some point in the Use Eval process, will you start to generate
concrete proposals for additions, modifications, etc. to the text in the
rec track document?
Overall, great stuff. Very readable and useful.
Mez
first cut usability walk through
Rachna Dhamija
to:
W3 Work Group
07/31/2007 09:24 PM
Sent by:
public-wsc-wg-request@w3.org
The usability group is starting to analyze the proposed recommendations.
Our first goal is to clearly state the expected user behavior in each
proposal and to map this to what is known from previous studies.
Proposal authors: Did we capture your expected user behavior correctly? Is
there anything you disagree with or would like to add?
http://www.w3.org/2006/WSC/wiki/RecommendationUsabilityEvaluationFirstCut
(Note: this is a work in progress- each write up is by a different author
and does not represent consensus by our group yet).
Rachna
Received on Friday, 10 August 2007 20:06:33 UTC