WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Jon Gunderson
Date: Apr 16, 2007 8:30PM

Peter,
One of the features of FAE is that the feedback is based on best practices rules and it tells the user what to do to fix the problem. So there no "manual" checks like in other systems. In the next release there will be even better developer feedback on what needs to be change din the markup to pass a rule. There are few warnings on a few rules.

You can get an FAE report directly from Firefox using the Firefox Accessibility Extension:

http://firefox.cita.uiuc.edu

Accessibility -> Tools -> FAE Report

This report actually sends the Firefox DOM representation of the document to FAE so it can check the accessibility of dynamically generated web content.

Please try it and let us know what you think.

Jon


---- Original message ----
>Date: Mon, 16 Apr 2007 17:08:09 +0200
>From: "Peter Krantz" < <EMAIL REMOVED> >
>Subject: Re: [WebAIM] Bringing accessibility into the development process (request for feedback).
>To: "WebAIM Discussion List" < <EMAIL REMOVED> >
>
>Jon,
>
>Thank's for your reply. I am not sure I completely understand the FAE so
>forgive me if some of these assumptions are wrong. Some issues I found
>developers to have with online tools in general are:
>
> 1. They are online meaning that it takes too much time to test a
> single page you are developing.
> 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.
>
>Is it possible to integrate FAE with functional testing tools such as Watir,
>HTMLUnit or Selenium?
>
>What type of user do you see using the FAE?
>
>Regards,
>
>Peter
>
>
>On 4/16/07, Jon Gunderson < <EMAIL REMOVED> > wrote:
>>
>> A tool we are developing at the University of Illinois is trying to go
>> beyond traditional accessibility checking and providing additional
>> evaluation information on the presence of functional accessibility features.
>>
>>
>