Also, as I said in my initial message, while WebCT campus edition has
the ability to create accessible pages, it is up to the author to make
sure that the pages are in *fact* accessible.  And, a number of the
features do things that the W3C depricates, like jumping to new windows
on links, without any clue that it has happened.

I was able to abuse them a bit on accessibility, and at least they are
thinking about it, so it should be possible for it to get better over
time.

As to the resource of compliant pages that are not accessible, that
would be a good addition to my ADA hall of shame, at
http://misericordia.edu/danson/HallOfShame.htm.  (And, yes, I just
realized that I don't have alt text on the pictures on this page.  I'll
go fix that.)

Denis Anson, MS, OTR
Computer Access Specialist
College Misericordia
301 Lake St.
Dallas, PA 18612
email: [log in to unmask]
Phone: 570-674-6413


> -----Original Message-----
> From: * EASI: Equal Access to Software & Information
> [mailto:[log in to unmask]] On Behalf Of David R. Stong
> Sent: Friday, March 15, 2002 11:06 AM
> To: [log in to unmask]
> Subject: Re: WebCT
>
> >There is a difference between complying with guidelines and actually
> >improving the usability for people with disabiltiies.
>
> Jon, this is a valid point that I find I always run up against. Do
> you maintain any resources that point out the discrepancies between
> what works and what's recommended? A collection of W3C guideline
> approved, 508 Regulation compliant inaccessible pages would be
> incredibly useful.
>
> My personal feeling is that Web information must be accessible,
> regardless of standards and guidelines that are awaiting future
> usability. Often, people prefer to stop when guidelines are met and
> potential lawsuit is avoided. Some sort of resource, even a list of
> non-functional guidelines, would be a big help.
>
> --
> David R. Stong, Graphic Designer
> 225 Computer Building, University Park PA
> Working for Universal Design:
> http://cac.psu.edu/training/outlines/accessibility