- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Thu, 17 Nov 2011 20:07:14 +0100
- To: Eric Velleman <E.Velleman@bartimeus.nl>
- CC: Eval TF <public-wai-evaltf@w3.org>
Hi Eric, Please find my comments below, updated according to the teleconference discussion earlier today (primarily changes to section 6). - On 17.11.2011 14:48, Shadi Abou-Zahra wrote: Please find below my comments on the current Editors Draft of the Methodology. The list probably looks more daunting than it is, they are really all minor editorial suggestions. The only point that may be worth more discussion is my suggested rewrite for section 6. I don't think others need discussion. Comments follow: # General comments - use consistent link texts -- ideally the link text reflects the target page title as closely as possible (for predictability); - avoid linking to external documents directly from the text -- link to the references or terminology section within this same document; - remove unnecessary editor notes; - make sure to have a space after the colons (in the editor notes) and capitalize the first word after the colon; # Section 1. Introduction - change "This WCAG 2.0 Evaluation Methodology (WCAG-EM) proposes an ..." to "The Website Accessibility Evaluation Methodology for WCAG 2.0 (WCAG-EM) is an ..."; # Section 2. Scope of this document - remove the editor note; - change "The WCAG 2.0 Evaluation Methodology describes a formal and harmonized way ..." to "The Website Accessibility Evaluation Methodology for WCAG 2.0 (WCAG-EM) is a standardized way ..."; - change "The Methodology defines manual and computer assisted methods ..." to "The Methodology defines manual and semi-automated methods ..."; - link "complete processes" to the definition within this same document; - change "The Methodology is an editors draft that provides guidance ..." to "The Methodology provides guidance ..." (there is a separate section for the status of the document); - change "WAI resource Conformance Evaluation of Websites for Accessibility" to "WAI resources on evaluating websites for accessibility" and link to http://www.w3.org/WAI/eval/; - change "Complementary WAI resources such as Preliminary Review of Websites for Accessibility and Involving Users in Evaluating Web Accessibility provide ..." to "It includes complementary resources on Preliminary Review of Websites for Accessibility and Involving Users in Evaluating Web Accessibility that provide ..." and link the documents; # Section 4. Target audience - remove the editor note; # Section 6. Expertise for evaluating accessibility - remove the editor note; - suggest this wording: [[ 6. Expertise required for using this methodology Users of the Methodology are assumed to be knowledgeable of WCAG 2.0, accessible web design, assistive technology, and of how people with different disabilities use the Web. Evaluation according to this methodology can be carried out by individuals but using review teams with combined expertise involving people with disabilities and older people in the evaluation process is strongly recommended. 6.1 Using Review Teams with Combined Expertise (Optional) The _W3C/WAI evaluation resource suite_ provides complementary guidance on _Using Combined Expertise to Evaluate Web Accessibility_. Review teams can provide better coverage of the expertise required in the understanding of web technologies, evaluation tools, barriers that people with disabilities experience, assistive technologies and approaches that people with disabilities use, and accessibility guidelines and techniques. 6.2 Involving People with Disabilities and Older People (Optional) The _W3C/WAI evaluation resource suite_ provides complementary guidance on _Involving Users in Evaluating Web Accessibility_. Evaluating with users with disabilities and with older users can identify additional issues that are not easily discovered by expert evaluation alone. It can make the evaluation process more effective and more efficient, especially when users are involved throughout the development process. Note: Although testing with users is not a requirement under this Methodology, we strongly recommend that people with disabilities and older people are involved in the evaluation process. ]] # Section 7.1 Technologies used on the webpages - expand or remove editor note; # Section 7.2 Base URI of the evaluation - expand or remove editor note; # Section 7.4 Complete processes - link "complete processes" to the definition within this document rather than to an external document; # Section 7.5 Key functionalities - add space after the colon in the editor note and capitalize "functionalities"; # Section 7.6 Webpages behind authorization - add space after the colon in the editor note; # Section 9. Evaluation - add something in the editor note that the Methodology will not provide WCAG 2.0 Techniques but rather explain how to use them effectively for evaluation; # Section 10.1 Conformity requirements - expand or remove editor note; Best, Shadi -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Activity Lead, W3C/WAI International Program Office Evaluation and Repair Tools Working Group (ERT WG) Research and Development Working Group (RDWG)
Received on Thursday, 17 November 2011 19:07:52 UTC