Here's more on the accessibility of WebCT. I'm just passing on the response
I received to my letter of inquiry to the instructor of an online course (at
the University of Wiscosnin-Madison) utilizing WebCT.
Axel Schmetzke
Library
University of Wisconsin-Stevens Point
-----Original Message-----
From: Debra Shapiro [mailto:[log in to unmask]]
Sent: Tuesday, January 09, 2001 11:55 AM
To: Schmetzke, Axel
Subject: RE: Basic Cataloging - an Internet Course
>Dear Dr. Shapiro,
>
>I have a question about your online cataloging course. Will people using
>screen reading software (with voice or Braille output) to access online
>information be able to enroll and succeed in this course. I am concerned
>that the "computer requirements," which call for a browser that will handle
>a frames format and javascript (Netscape Navigator or Internet Explorer,
>versions 4.02 or higher), make it impossible for students using screen
>readers to participate in this course.
>
>I look forward to your response,
>
>Axel Schmetzke, Ph.D.
>Library
>University of Wisconsin-Stevens Point
>
Basically, I am using WebCT to present the course, since this is the
courseware that UW is supporting at the moment. If asked to make
accomodations for someone needing to use a screen reader, I am more
than willing to do so. To find out how technically possible this is,
I forwarded your query to the WebCT people at DoIt, and I believe I
got a postive reply:
>From WebCT: "WebCT 3.0 underwent a big initiative to increase the
>W3C Level 1 compliance. Level 1 is close to 100%, Level 2 84% and
>Level 3 falls off.
>We are continuing this effort moving onto WebCT 4.0 (Cobalt). One
practical
>metric to use is screen readers (JAWS). If a screen reader can
>navigate a course, it's a benchmark. WebCT does a good job with
>readers. We have also extended
>our instructions (since there is a lot of customization of content) within
>the product help and the e-learning hub http://www.webct.com to help
>designer code html that complies with the W3C standards."
>
>We are trying to get more specifics from WebCT on exactly how they
>are meeting the level 1 and 2 W3C compliance levels. We have had a
>visually disabled person from the Trace Center and another one from
>DoIT look at WebCT with JAWS, a high end screen reader. Since JAWS
>can read frames (some of the low-end screen readers may not be able
>to), in general, WebCT did OK. It helps to have a sighted person to
>work along with the visually disabled person. One suggestion is to
>create some notes that describe what is being displayed on the
>course pages, to help with navigation. Theoretically, this could be
>done in the course itself.
>
>Besides making any pages the course leader designs accessible
>(there's lots of information on this, including the accessibility
>topic in the WebCT designer on-line help, plus LTDE's accessibility
>web site, http://www.doit.wisc.edu/accessibility/), there are a few
>configuration settings you can play with in WebCT. Students and
>designers can hide the navigation bars if they want just one frame
>displayed. If designers expect this, they shouldn't put any
>important navigation links on the bar. Designers can also suppress 2
>frames in content; don't show Table of Contents and page itself in
>separate frames. They can just show the Table of Contents, or the
>content itself.
>
>Hope this helps. I plan to continue to work with LTDE and WebCT
>regarding WebCT's accessibility, in addition to doing testing in
>LTDE's lab with screen readers. In summary, making content and the
>course design is up to the course designer. Making the program,
>WebCT, more accessible is up to the developer.-Hildy
In practice, in my course, I generally do hide the Navigation bars,
and do not put any important navigational elements there, and just
show content itself. I would be willing to build in any explanatory
notes needed.
Best regards,
debra.
--
[log in to unmask]
Debra Shapiro
Continuing Education Services
UW-Madison SLIS
4282 Helen C. White Hall
Madison WI 53706
608 262 9195
FAX 608 263 4849
|