Forum .LRN Q&A: Making Online Learning Accessible - Guidelines Released

http://ncam.wgbh.org/news/pr_09192002.html

I just found this. We definitely want to make it easy to develop accessible web sites with OpenACS and dotLRN.

Collapse
Posted by Dave Bauer on
Direct link to guidelines: http://ncam.wgbh.org/salt/guidelines/
It's great that you've found these guidelines. We should read them through carefully and try to sift out the good and not so good stuff.

Knowing how sparse/plain the OpenACS UI is in general, I suppose it's a matter of considering adding to the toolkit rather than subtracting from it...which is fortunate for us (thanks, again, to the Greenspun philosophy😉.

The IMS specifications I've read so far have expressively refrained from saying anything about UI issues and about how the different specifications ought to be implemented. When it comes to what the users experience, in terms of usability/accessibility and so on, I find it a good thing they've spit out a policy.

In the guidelines they even mention Wimpy Point as one of several good presentation tools ...

http://ncam.wgbh.org/salt/guidelines/sec6.html

i hope they mention WimpyPoint and the oACS! WGBH was one of aD's gem clients.

talli

Collapse
Posted by Dave Bauer on
Talli,

Sorry, its links to the aD download repository which redirects to a RedHat CCM Community page.

Here is a cookbook like accessibility resource (uses Movable Type in some examples):

http://diveintoaccessibility.org/table_of_contents.html

that is very well done (it wants to be read and not just skimmed). Maybe it will motivate some to start making their OpenACS sites more accessible.

Carl

P.S. Sadly the Wimpy Point version in 4.x has some major problems, which makes it almost unusable (I posted the problems I found in the old sdm)