RE: NOtes from GL meeting 12/10/02

under (c) we also talked about a 4th category

4) Things that might be good to do in some situations and might be bad
to do in others.  

The example we were discussing was making the design "simple".  In some
situations, a single complex page can be easier to use than a collection
of simple pages.  Stating that a simple page is always easier would be
misleading, and a site designer should think very carefully about how to
organize things to make them easy to use.


-----Original Message-----
From: Gregg Vanderheiden [mailto:GV@TRACE.WISC.EDU] 
Sent: Thursday, January 10, 2002 4:24 PM
To: GLWAI Guidelines WG (GL - WAI Guidelines WG)
Subject: NOtes from GL meeting 12/10/02

Notes from today's GL telecom.  



a)  No claim of conformance unless you meet ALL of the Minimum set of
checkpoints (this is restatement of old consensus item)


b)  Whether you claim compliance with a particular checkpoint or not -
there should be a mechanism for reporting what you have done on that
checkpoint.  That is listing of which Requirements and or supplementary
items were done 



c)   for each checkpoint we might think of the items below the
checkpoint as falling into three categories of recommendations for
making sites or pages accessible 

1.	Requirements for this checkpoint 
o	(items which are both Essential and testable)  
o	(must do all to claim compliance)  
o	(all is sufficient to claim compliance)
2.	Additional items that are recommended for most sites
o	Do not need to do these but should.
o	Includes items that are 
*	important but not testable
*	testable but not essential for all sites
3.	Key items for tuning a site for accessibility along this
dimension 
o	Includes additional things that could be done if really
interested in making sure a page or site did a really great job along
this dimension.
o	(see also techniques document for additional ideas and
alternatives)



Notes from discussion of 3.1  (see also notes from last meeting)


3.1   Use simple / clear /consistent / predictable presentation.    (We
are working on it)  [wherever possible and effective] 

 -  Present elements (e.g. navigational, informational and action
elements) consistently (e.g. order and format) on the "pages" of a
site/section.
 -  Document structure elements should be essentially the same in
presentation when in the same "page" or "section" (of the site or page).
 -  Document structure elements should be similar enough in presentation
on different pages/section to be easily recognized as having the same
function.  
 -  (see also checkpoint 2.2 that covers things that are similar in
presentation having similar or predictable behavior)
 -  NOTE there are different levels of relatedness depending on how
close things are in the site hierarchy. 
 -  Use common presentational conventions. 
 -  need to add items for other goals (clear, simple?)       

Comments: 	- What about when it is better design and easier to use
and understand if it is not consistent? 
 		- What about if you go to a new type of information and
you should change layout to match?









-- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Human Factors 
Dept of Ind. Engr. - U of Wis. 
Director - Trace R & D Center 
Gv@trace.wisc.edu <mailto:Gv@trace.wisc.edu>, <http://trace.wisc.edu/> 
FAX 608/262-8848  
For a list of our listserves send "lists" to listproc@trace.wisc.edu
<mailto:listproc@trace.wisc.edu>

Received on Thursday, 10 January 2002 19:55:27 UTC