[Accessibleweb] AccessibleWeb@U - Tools - December 20, 11:30am, MGH 015L

Pace Arko jsay at ngtvoice.com
Thu Dec 13 12:41:43 PST 2007

Hello everyone,

I too won't be able to attend this meeting but I do have recommendations:

Windows, XP, Vista:

Making certain your markup is kosher by your declared DTD is a very helpful
start to accessible web design. If you are working with static HTML files I
recommend TidyGUI:


(Actually with a little tweaking and copy and paste, you can use it to check
any markup you have in CMS templates too. It won't choke on most PHP and ASP
code provide everything is properly delimited. Don't know about ASP.Net
though. The other nice thing about TidyGUI is that you can run it from the
command line for bulk clean up of static files too. )

If you are working with a large number of static HTML files, I strongly
recommend ARV:


It's much faster than checking things against the W3C validator and it's
based on a SGML parser so you know it ain't lyin'. It's shareware but it's
worth it.

EA's recommendation of WAVE is better but, just as an alternative since I've
used it for so long, I'll throw out A-Prompt's page testing tool:


For captioning video, I recommend MAGpie:


It will generate captioning in either in SMIL or Microsoft's proprietary
SAMI formats. They also have this tool for OSX.

I have some other recommendations but they kind of depend on how technical
people want to get here. Any Java developers looking for applet tips on this

Finally a couple of websites you may have heard of here:


That's it. Hope that helps,

Pace Arko,
J-Say Product Specialist, Webmaster,
Next Generation Technologies, Inc.
20006 Cedar Valley Rd - Suite 101
Lynnwood, WA 98036-6334
Tel: 425.744.1100, extension 17
(The best time to reach me live
is between 8:30AM and 12:30PM
Pacific Time.)
Fax: 425.778.5547

-----Original Message-----
From: accessibleweb-bounces at mailman1.u.washington.edu
[mailto:accessibleweb-bounces at mailman1.u.washington.edu] On Behalf Of E.A.
Sent: Wednesday, December 12, 2007 11:53 AM
To: 'Rick Ells'; accessibleweb at u.washington.edu
Subject: RE: [Accessibleweb] AccessibleWeb at U - Tools - December 20, 11:30am,
MGH 015L

Please accept my apologies for not being able to attend this meeting but I
would really love to learn the results of your deliberations as it is a
subject we have been discussing in the lab.
My list includes
WAVE from webaim
WebbIE with Thunder screenreader
Opera in several modes
Firefox Mozilla with Firefox Accessibility Extension inc. FAE from Illinois
and Web developer extension plus Accessibar.
Internet Explorer with Web Accessibility Toolbar.

I am not a web developer but use Dreamweaver to put the LexDis website
together and Xerte to show any flash files and the Illinois wizard for
PowerPoints - I am now testing assistive technologies with Vista and just
hope the team can offer the illinois wizard in a Vista version ASAP!

Hope this helps and I am looking forward to learning from your
deliberations, as I have to evaluate many Web 2.0 sites over the coming
months and would love to have a useful toolkit to hand!

Have a very happy Christmas and New Year.

Best wishes E.A.

Mrs E.A. Draffan
Learning Societies Lab,
ECS, University of Southampton,
Tel +44 (0)23 8059 7246

-----Original Message-----
From: accessibleweb-bounces at mailman1.u.washington.edu
[mailto:accessibleweb-bounces at mailman1.u.washington.edu] On Behalf Of Rick
Sent: 12 December 2007 17:20
To: accessibleweb at u.washington.edu
Subject: [Accessibleweb] AccessibleWeb at U - Tools - December 20, 11:30am, MGH

Topic: Good Tools, Not So Good Tools
Speaker: Discussion - come and contribute
Date: Thursday, December 20, 2007
Time: 11:30a.m. - 1:00p.m.
Location: Mary Gates Hall, Room 015L

Come join us for a discussion of what tools help us create
accessible Web sites, and which make reaching that goal more
difficult than it needs to be. This discussion supports
work Terry Thompson is doing to create a central UW Web site
about accessibility. Here is Terry's query from a message he
sent to the Access email list:

Does anyone have tools that they utilize in their
development work that they feel either support
accessibility well, or do NOT support accessibility well?
By "tools" I mean literally anything - web authoring
tools, content management systems, toolbars, plug-ins,
accessibility checkers - We're hoping to put together a
fairly comprehensive list.


More information about the Accessibleweb mailing list