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

Re: approval

From: <accessys@smart.net>
Date: Mon, 20 Feb 2012 18:22:02 -0500 (EST)
To: Karl Groves <karl@karlgroves.com>
cc: David Woolley <forums@david-woolley.me.uk>, WAI Group <w3c-wai-ig@w3.org>, Meliha Yenilmez <melihayenilmez@yahoo.com>
Message-ID: <Pine.LNX.4.60.1202201820400.30501@cygnus.smart.net>

well hopefully on this mail group we have enough of those different people 
that we will be able to pretest as much as possible to get these 
guidelines as "accessible" as possible.


On Mon, 20 Feb 2012, Karl Groves wrote:

> Date: Mon, 20 Feb 2012 18:10:01 -0500
> From: Karl Groves <karl@karlgroves.com>
> To: David Woolley <forums@david-woolley.me.uk>
> Cc: WAI Group <w3c-wai-ig@w3.org>, Meliha Yenilmez <melihayenilmez@yahoo.com>
> Subject: Re: approval
> Resent-Date: Mon, 20 Feb 2012 23:10:30 +0000
> Resent-From: w3c-wai-ig@w3.org
> On Mon, Feb 20, 2012 at 5:02 PM, David Woolley
> <forums@david-woolley.me.uk> wrote:
>> To find out if it is actually accessible, you need to find people with lots
>> of different disabilities and perform a usability survey on them, allowing
>> them to use their own browsers and any assistive technology that they use.
> Do you do this?  Really?
> With all due respect, this is exactly the type of attitude that
> perpetuates the impression that accessibility is nebulous, expensive,
> and difficult.
> It would be wonderful to be able to test with real users, but such a
> thing is often not feasible due to time, budget, or resource
> constraints.  Considering the other types of testing available that
> can be used to gather accessibility data, doing usability testing
> should be reserved for cases where other test approaches (that are
> often quicker, cheaper, and easier anyway) have already been utilized.
> Karl
Received on Monday, 20 February 2012 23:23:06 UTC

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