E-mail List Archives
Re: Bringing accessibility into the developmentprocess (request for feedback).
From: Patrick H. Lauke
Date: Apr 16, 2007 9:30AM
- Next message: tedd: "Re: Bringing accessibility into the development process (request for feedback)."
- Previous message: tedd: "Re: Validation equals Accessibility?"
- Next message in Thread: tedd: "Re: Bringing accessibility into the development process (request for feedback)."
- Previous message in Thread: Peter Krantz: "Re: Bringing accessibility into the development process(request for feedback)."
- View all messages in this Thread
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
- Next message: tedd: "Re: Bringing accessibility into the development process (request for feedback)."
- Previous message: tedd: "Re: Validation equals Accessibility?"
- Next message in Thread: tedd: "Re: Bringing accessibility into the development process (request for feedback)."
- Previous message in Thread: Peter Krantz: "Re: Bringing accessibility into the development process(request for feedback)."
- View all messages in this Thread