WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Procedure of making web accessibility testing.

for

From: Jon Gunderson
Date: Jun 10, 2009 8:10AM

A free service from the university of Illinois can be used to test multiple pages as part of an accessibility audit program:

http://fae.cita.illinois.edu/

You must sign up for a free user account to test multiple pages:
http://fae.cita.illinois.edu/accounts/register/

Accessibility reports can be archived and the URL to the report can easily be shared to provide feedback to developers and administrators on accessibility problems.

The rules used in FAE are based on the iCITA best practices:
http://html.cita.uiuc.edu

Jon





---- Original message ----
>Date: Tue, 9 Jun 2009 09:47:19 -0700 (PDT)
>From: "J. B-Vincent" < <EMAIL REMOVED> >
>Subject: Re: [WebAIM] Procedure of making web accessibility testing.
>To: WebAIM Discussion List < <EMAIL REMOVED> >
>
>A tool I've been using lately for sampling pages is Link Sleuth, which is available free from http://home.snafu.de/tilman/xenulink.html. When it opens, hit Ctrl-N, and paste in the URL for the home page of the site you want to check. After it runs (and for some sites, it can take a looooong time), click on the "type" header, and then look for the "text/html" files. This helps me identify pages that may have distinct problems, as well as groups of pages likely to have common problems. It also gives me a clear overview of the site so I can make sure I'm getting a fair sample.
>
>--Jane Vincent, Center for Accessible Technology
>
>--- On Tue, 6/9/09, Angela Colter < <EMAIL REMOVED> > wrote:
>
>From: Angela Colter < <EMAIL REMOVED> >
>Subject: Re: [WebAIM] Procedure of making web accessibility testing.
>To: "WebAIM Discussion List" < <EMAIL REMOVED> >
>Date: Tuesday, June 9, 2009, 7:27 AM
>
>Hi Rakesh,
>
>I recently worked on an accessibility evaluation for a recently redesigned
>association web site. Now, the full site has around 60,000 pages; there are
>many, many content editors updating different areas of the site.
>
>Because of the limited budget of the project, we reviewed a sample of 15
>pages across the site, chosen by the client. While focusing on most popular
>pages certainly makes sense, our samples were chosen in an effort to ensure
>that the main content areas (each edited by a different group) were
>represented. That way, no one could look at our results and think, "well,
>that's a problem for THAT group, but not for ours." That was the thinking
>behind choosing the sample, anyway.
>
>What we found was there were two different types of accessibility errors:
>errors in the design and errors in the content.
>
>The "design" errors (such as text links that were styled so that the
>underlines were removed) were located in the page templates, CSS, etc. These
>errors would need to be corrected by folks with specialized knowledge or
>access to fix these global issues. And because they were global, fixing them
>once fixed them everywhere.
>
>The "content" errors (such as poorly chosen or missing alt text) were
>usually introduced by the content editors themselves. These are easy enough
>to fix once the content editors understand what the errors are, how the
>affect accessibility and how to fix them. The problem is, content errors are
>very easy to reintroduce.
>
>So by all means, do an accessibility review on a selection of pages. My
>suggestion would be to consider your popular pages, critical tasks,
>different page types (forms vs. pages, for example), and the different
>content editors in your sample.
>
>Where you find global issues in the design, fix them. Where you find errors
>introduced by the content editors, focus your accessibility training efforts
>to address the types of errors you're content editors are making.
>
>Hope this helps,
>
>Angela Colter
>
>Usability / Accessibility Consultant
>angelacolter.com
>
>On Tue, Jun 9, 2009 at 12:18 AM, Rakesh Chowdary Paladugula <
> <EMAIL REMOVED> > wrote:
>
>> Dear all,
>>  I have a doubt from the beginning. I have a existing website with
>> 1000 pages to be tested for web accessibility should I test all the
>> 1000 pages or some selected pages . If so what are the pages I gave to
>> test.
>>  One more issue is I will have websites under construction which will
>> be in local surver. Wave will not take the URL of the staging site. Is
>> the procedure used is file upload and copying the source code and
>> validate or is there any other procedure.
>>  Thanks & regards
>> Rakesh Chowdary
>> Iridiuminteractive Limited
>> Changing a face doesn't change anything but facing a change changes
>> everything.
>>