W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2006

Re: Betr.: [Demo] Evaluation Report

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 13 Mar 2006 13:50:22 +0100
Message-ID: <44156A8E.4080407@w3.org>
To: Eric Velleman <E.Velleman@bartimeus.nl>
Cc: w3c-wai-eo@w3.org

Hi Eric,

Thank you for your input. Please find some comments below:

Firstly, we did not set a requirement to follow EN 17020 ("General criteria for the operation of various types of bodies performing inspection"), nor is this report (and the whole demo) intended to be a best practice resource for certification. The goal of this deliverable is to help raise awareness on Web accessibility issues, and provide developers with concrete examples. Please see "Using the Demonstration" section for more background:
  <http://www.w3.org/WAI/EO/2005/Demo/#howto>

Secondly, we may add other types of reports (and/or educational resources) to expand the demo as we go along but for now we chose to provide the more educational approach for the report. Many organizations provide boilerplate information about the issues encountered during an evaluation review within their audit reports, in order to help developers better understand the issues and achieve more sustainable level of quality. Also our evaluation template has a section about "Results and Recommended Actions" (as opposed to "results" only):
  <http://www.w3.org/WAI/eval/template.html#results>

All in all, it seems to me that we need to better clarify the scope and intent of this report (and the demo as a whole). "Meta-introduction" as someone suggested during the previous EOWG call...

Regards,
  Shadi


Eric Velleman wrote:
> Hello Shadi,
> 
> Very much like your document and the before after website. We use the
> evaluation report template for our reports all the time. We do about 150
> website evaluations per year and the reactions on the format are very
> good.
> But in the reports, we  cannot add the advice as you did because of EN
> standard EN17020. Evaluators cannot give advice. That would more or less
> compromise the independance of their (next) evaluation. Also in doing
> this you/we would be repeating ourselves all the time as we see the same
> problems on many websites. As a solution, we point to a seperate
> brochure with all the explanations and many practical code examples. If
> we encounter a new problem, we add a new part to the brochure. My advice
> would be to take the advice out and point to another resource for that
> like the curriculum.
> 
> Also it would be good to add the resources that were in the
> scope/sample at the end of the document, although it is quite obvious
> what they are in this case. For larger websites, this is very
> interesting and necessary for conformancy with evaluation standards.
> 
> Kindest regards,
> 
> Eric Velleman
> Accessibility Foundation
> www.accessibility.nl
> 
> 
> 
> 
> 
>>>> Shadi Abou-Zahra <shadi@w3.org> 10-3-2006 13:48:05 >>>
> 
> Dear Group,
> 
> Apologies for the delay in sending this so shortly before the meeting,
> I've been trying to put in everything we need for discussion on today's
> call.
> 
> Please find the evaluation report for the Before/After Demo (BAD):
>   <http://www.w3.org/WAI/EO/2005/Demo/report>
> 
> Note: each of the sections in this report has enough content for
> intense discussions so I propose that we use today's time to focus on
> the overall structure and organization of the report. Specifically the
> following aspects:
> 
> * If you were expecting an evaluation report for your Web site, is this
> the type of information you would want in it? (Consider being a manager
> or a developer)
> 
> * If you were writing an evaluation report for a Web site, does this
> report help you as a model to follow?
> 
> * If you wanted to learn more about Web accessibility, does the
> evaluation sufficiently outline some of the issues?
> 
> 
> Looking forward to your input.
> 
> Regards,
>   Shadi
> 
> 

-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe | 
Chair & Staff Contact for the Evaluation and Repair Tools WG | 
World Wide Web Consortium (W3C)           http://www.w3.org/ | 
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | 
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ | 
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France | 
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 | 
Received on Monday, 13 March 2006 12:50:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:38 UTC