Re: Simplicity of Authoring and Accessibility Tools

One of our committee members wrote "Six Steps to Accessibility
Certification" at:   It
describes the process she went through to ensure that her agency site was in
compliance with our state policy
A few other people here have tried it and it seems to work well. Please
note, however, one of the tools we use only works with FrontPage 2000, and
these steps are performed to ensure compliance with our policy, not Section

Kathleen Anderson, Webmaster
Office of the State Comptroller
55 Elm Street
Hartford, Connecticut   06106
voice: 860.702.3355 fax: 860.702.3634

----- Original Message -----
From: Gatewood, Joy <>
To: <>
Sent: Friday, January 19, 2001 2:56 PM
Subject: RE: Simplicity of Authoring and Accessibility Tools

> I use a combination of tools to discover what fixes are needed
> to improve accessibility.
> -Linkbot has a web site scan that includes a listing of pages missing
> attributes (such as images missing alt tags and pages without titles);
> -Dreamweaver also has these options;
> -Homesite (I use the 3.2 old version with a built in HTML validator)
> lets you run the validator over a web page and see not only the HTML
> errors, but also prompts the user to add alt tags to images lacking them;
> -Bobby is useful to find problems with your web site/page that you may
> have overlooked; and
> -JAWS is also useful to beta test your site with, especially to mimic a
> blind
> person's visit to your site.
> Then one can consult a checklist and go over it manually to fine tune
> any errors and/or omissions.
> I'd be interested to hear what others use.
> Joy Gatewood
> Vector Research, Inc.
> -----Original Message-----
> From: Charles McCathieNevile []
> Sent: Friday, January 19, 2001 12:19 PM
> To: Kynn Bartlett
> Cc: Charles F. Munat;
> Subject: RE: Simplicity of Authoring and Accessibility Tools
> I also agree that we need a good tool. For my pusrposes, I use Amaya as a
> WYSIWYG tool. It doesn't do everything, but it does the things I need.
> is my compromise. (In particular, it suffers from being somewhat
> inaccessible
> to a number of users. On the other hand it has an interface that makes it
> fairly easy to create reasonably structured content, although it is not
> same interface as many common editors. I guess I should confess that I
> actually don't find those editors intuitive either - I have to learn every
> single piece of software I want to use).
> There was a thread a while ago on editors that people like using. I
> it was very valuable to see what people liked and why, and what the
> limitations were.
> cheers
> Charles McCN
> On Fri, 19 Jan 2001, Kynn Bartlett wrote:
>   At 1:48 AM -0800 1/19/01, Charles F. Munat wrote:
>   >As for teaching HTML, I've been teaching for the better part of 20
> and
>   >I've yet to meet anyone who was incapable of learning. Different people
> may
>   >need different pedagogical techniques, and may learn at different
> but
>   >anyone who's capable of operating FrontPage is certainly capable of
> learning
>   >enough HTML to code a web page. Whether they want to is another
>   >For those who don't, I hope we get a decent WYSIWYG tool soon.
>   We are in definite agreement that we need a good WYSIWYG tool.  I
>   don't think there are any at the moment, sadly, so compromises are
>   often necessary.
>   --Kynn
> --
> Charles McCathieNevile    phone: +61 (0) 409 134
> 136
> W3C Web Accessibility Initiative
> Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
> until 6 January 2001 at:
> W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex,
> France

Received on Friday, 19 January 2001 15:09:49 UTC