- From: <kvotis@iti.gr>
- Date: Thu, 13 Mar 2014 13:02:50 +0200
- To: "Detlev Fischer" <detlev.fischer@testkreis.de>
- Cc: public-wai-evaltf@w3.org, evelleman@bartimeus.nl
I Would agree also with Detlev;s comment because this may be more interesting regards kostas > Hello Eric, > > What happened to the idea to let evaluators pick any site they like to > evaluate, to get a nice range of different websites? Is this a draft still > to be confirmed or possibly changed in today's telco? > > I think it would be highly desirable to get feedback, for example, on > using WCA-EM on web-apps even if that doesn't add to the (comparable) test > results for the one site identified in the online survey. > > Best, > Detlev > > -- > Detlev Fischer > testkreis c/o feld.wald.wiese > Thedestr. 2, 22767 Hamburg > > Mobil +49 (0)1577 170 73 84 > Tel +49 (0)40 439 10 68-3 > Fax +49 (0)40 439 10 68-5 > > http://www.testkreis.de > Beratung, Tests und Schulungen f?r barrierefreie Websites > > Velleman, Eric schrieb am 13.03.2014 11:41: > >> Dear all, >> >> Eval Task Force invites organizations and persons who (professionally) >> evaluate >> websites for WCAG 2.0 to test-run the Web Content Accessibility >> Guidelines >> Evaluation Methodology (WCAG-EM 1.0 Public Working Draft) at: >> http://www.w3.org/TR/WCAG-EM/ >> >> We ask you to evaluate a full website using WCAG-EM and providing your >> input >> through a survey. The website for the test-run is listed in the survey. >> For the >> reporting (both on the evaluation and on the use and clarity of the >> evaluation >> methodology, we ask you to input your results into the survey at: >> https://utwentebs.eu.qualtrics.com/SE/?SID=SV_cGAAMLdmjk3FmHX >> by *10 april 2014* >> >> Please note that this evaluation could take several hours or days >> depending on >> your workflow. The data will be treated as confidential and used to >> analyze >> improvements to WCAG-EM. Data you provide will always be anonymous. >> >> Overview: >> WCAG-EM describes an approach for evaluating how websites -- including >> web >> applications and websites for mobile devices -- conform to Web Content >> Accessibility Guidelines (WCAG) 2.0. It covers different situations, >> including >> self-assessment and third-party evaluation. It is independent of >> particular >> evaluation tools, web browsers, and assistive technologies. >> >> Additional questions: >> You can send any additional comments or questions about this test-run of >> WCAG-EM to the publicly archived mailing list: >> public-wai-evaltf@w3.org >> >> Background: >> WCAG-EM is developed by the WCAG 2.0 Evaluation Methodology Task Force >> (Eval >> TF), a joint task force of the Web Content Accessibility Guidelines >> Working >> Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG). >> The >> Eval TF is introduced at: <http://www.w3.org/WAI/ER/2011/eval/eval-tf>. >> It is a supporting resource for WCAG 2.0 and does not replace or >> supersede it >> in any way. For an overview of WCAG, see >> <http://www.w3.org/WAI/intro/wcag> >> This work is developed with support of the EC-funded WAI-ACT Project >> (IST >> 287725) described at: <http://www.w3.org/WAI/ACT/> >> It is part of W3C WAI activities on web accessibility evaluation and >> testing >> introduced at: <http://www.w3.org/WAI/ER/2011/eval/> >> >> URI: >> The first URI above goes to the latest version of the document. The >> "dated" >> version of this draft is: >> <http://www.w3.org/TR/2014/WD-WCAG-EM-20140130/> >> The difference between these URIs are explained in Referencing and >> Linking to >> WAI Guidelines and Technical Documents at: >> <http://www.w3.org/WAI/intro/linking.html> >> >> Please let us know if you have any questions. Thank you in advance for >> participating in this evaluation test-run. >> Feel free to circulate this message to other lists, but also to other >> organizations and persons who professionally evaluate websites for WCAG >> 2.0; >> please avoid cross-postings where possible. >> >> Regards, >> Eric Velleman, Eval TF Facilitator >> Shadi Abou-Zahra, W3C/WAI Staff Contact >> >> > >
Received on Thursday, 13 March 2014 11:03:16 UTC