E-mail List Archives

Re: Bringing accessibility into thedevelopmentprocess (request for feedback).

for

From: smithj7
Date: Apr 21, 2007 5:50AM


I agree with Patrick regarding the need for user input. For example, I
had a form on our site (note wasn't used much - been there 10 years) and
it was html that of course past ever accessiblity and evaluation test.
However, our users got used to being able to download a form (rich text
format) and complete it using their computers. The html form was not
usable for this.

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Patrick H.
Lauke
Sent: Monday, April 16, 2007 11:25 AM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Bringing accessibility into the developmentprocess
(request for feedback).


Quoting Peter Krantz < <EMAIL REMOVED> >:

> 2. They require manual intervention to do the test (which takes
time).
> 3. They typically provide feedback that you have to be able to
> interpret to make use of. E.g. some warnings from the FAE may be
> irrelevant but it is hard to know if you don't know accessibility.

You're not going to get an automated tool that can tell you if a
resource is accessible or not, on its own. There ALWAYS needs to be
human/manual intervention and review, at least for part of the tests
that can be performed. Any tool that pretends to give you an
authoritive answer without human intervention is lying.

P
--
Patrick H. Lauke