- From: Michael S Elledge <elledge@msu.edu>
- Date: Thu, 14 Jun 2012 09:47:31 -0400
- To: Alistair Garrison <alistair.j.garrison@gmail.com>
- Cc: Kerstin Probiesch <k.probiesch@googlemail.com>, Eval TF <public-wai-evaltf@w3.org>
Hi Everyone-- Could we use the terms "evaluation techniques" and "developer techniques" to differentiate them? Otherwise this gets mighty confusing. Mike On Jun 14, 2012, at 9:17 AM, Alistair Garrison <alistair.j.garrison@gmail.com> wrote: > Hi Kerstin, > > Shadi's responses to my questions were respectfully clear. This is not part of Shadi's attempted summary, so I have changed the thread. > > I'd still like to know how you (Kerstein Probiesch) actually know when 'Rome' is reached? And, again I would ask - Do you follow a check list, or is it gut feeling? > > Alistair > > On 14 Jun 2012, at 14:10, Kerstin Probiesch wrote: > >> Hi Alistair, >> >> even if a technique can be submitted it doesn't mean that it will be >> submitted. Until a technique is accepted and an updated version of WCAG2 is >> published time goes by and it would mean, that a working technique couldn't >> be used because it is not part of the techniques document. We should also >> consider that we speak not only about HTML and ARIA but also about PDF, >> where there are discussions about (as I understood 'differences') between >> WCAG 2.0 techniques and PDF/UA techniques. >> >> There are many ways to rome and a way is successful if rome is reached, even >> when the route is not one of the suggested route in existing street maps. >> Let's see the WCAG 2.0 as something like this: even when I don't think about >> going to rome but to a friend's house in an area nearby google maps gives me >> a route which would indicate, that I have to follow a route which will take >> me a 17 minutes (walk). Instead of taking this route I tested a small way
Received on Thursday, 14 June 2012 13:50:38 UTC