WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bringing accessibility into the development process(request for feedback).


From: Peter Krantz
Date: Apr 16, 2007 10:30AM

On 4/16/07, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> 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.

That can be a problem in my opinion. A project typically is staffed with
designers (influencing e.g. color contrast), developers (influencing markup)
and content editors (influencing content). Instead of having one tool that
fits none of these roles I propose that there should be tools that target
each role individually.

Also, the strife for a definitive "Yes! Your page is completely accessible"
does not rule out tools that give you feedback on various parts of

Raakt, for example, targets markup developers by trying to become a part of
the toolsets they already use (functional testing frameworks). Instead of
not using any tool at all I have tried to lower the barrier to at least do
some checking while you are developing.