W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > April 2012

Templates and use cases

From: Detlev Fischer <detlev.fischer@testkreis.de>
Date: Thu, 19 Apr 2012 17:29:04 +0200
Message-Id: <B9DA023B-A309-4582-8672-7D18961AD1C2@testkreis.de>
To: Eval TF <public-wai-evaltf@w3.org>
Hi list,

just two points that cam to mind after today's teleconference:

(1) Templates

The text now (in Step 2a)  talks about "The common web pages of the  
website and templates available to the evaluator"

For templates that just cover a part of the web page (e.g. portlets),  
some aspects of conformance depend on their place in the context of  
the overall page - think of 1.3.1 and 2.4.1 (heading levels), 1.3.2  
Meaningful Sequence, etc. I wonder what the evaluator will actually  
*do* with the templates provided by the commissioner - if they are  
empty or out of page context, a complete evaluation seems impossible  
or of doubtful value. But this may not be intended by the description  
- not sure. Many observations (potential fails) also result from  
interactions between template and content on a real page.

I am not against taking stock of templates per se, just not sure what  
added value that would bring and how they would be assessed outside a  
normal page context. Thoughts?

(2) Use cases

In cases where evaluations of web applications are commissioned by  
clients, checking the use cases provided is certainly a good starting  
point. It's just important to also go beyond documented use cases,  
especially regarding error handling and unexpected user actions, to  
capture violations.


-- 
Detlev Fischer
testkreis - das Accessibility-Team von feld.wald.wiese
c/o feld.wald.wiese
Borselstraße 3-7 (im Hof)
22765 Hamburg

Tel   +49 (0)40 439 10 68-3
Mobil +49 (0)1577 170 73 84
Fax   +49 (0)40 439 10 68-5

http://www.testkreis.de
Beratung, Tests und Schulungen für barrierefreie Websites
Received on Thursday, 19 April 2012 15:22:20 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:52:13 GMT