WCAG 2.0 and scripting

I've recently been dealing with a software provider, whose software my company
installed on behalf of our client, with assurances that the software is
'accessibility compliant'. When the client asked for an audit i was asked to
provide a report: it nearly meets WCAG 1.0 Level A compliance; most of the
issues are minor and can be fixed with reasonably little effort. 

The biggest stumbling block in meeting Level AA compliance, is that the
software is reliant on javascript to deliver a critical part of its
functionality. This is not easy to fix. 

Software provider is trying to claim that they are developing to WCAG 2.0
standards and that under WCAG 2.0 it would be possible to claim compliance,
despite the fact that this functionality provided via Javascript may not be
available to all users.

I would love to hear what the opinion of this group are in this regard; and
whether there is an authoritive answer in this regard.


Kind Regards
Harry
mob: +44 794 034 3919

~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~
Good judgement comes from experience.
Experience, of course, is the result 
of poor judgement.
               - Geoff Tabin

Received on Wednesday, 26 September 2007 10:10:26 UTC