RE: WCAG 2.0 and scripting

> If done the right way, Javascript can work fine with AT like screen 
readers . . .
> Granted, this shuts out users who (through choice, or situations beyond 
their control) 
> can't/won't run Javascript, but I believe that under WCAG 2.0 that's 
fine 
> (as it's about access for users with disabilities, not "universal 
access").
> IMHO, of course.
> Patrick

Well said Patrick.

Although I think "it's about " can be more than WCAG 2.0.  Many of us, 
including you, me and others are also trying to make internet access more 
affordable, but WCAG 1.0 does not make the internet more affordable per 
se.  No one is paying less to turn JavaScript off. . . 

And as I said before, access to JavaScript should be like getting access 
to the front door, or HTML, or multimedia.  People with disabilities want 
to interact with JavaScript rich sites for the reasons everyone else does, 
regardless of disability - but that is a policy discussion.  WCAG 1.0 and 
2.0 is about a set of technical standards.

The WCAG 2.0 FAQs answer the question as to when to start using WCAG 2.0 
and list the benefits of starting now - see 
http://www.w3.org/WAI/WCAG20/wcag2faq.html#start
        There are many benefits to using WCAG 2.0 Working Drafts in your 
current and upcoming projects:
WCAG 2.0 is more applicable to current technologies, future technologies, 
and non-W3C technologies. 
WCAG 2.0 supporting documents, such as Understanding WCAG 2.0, provide 
more information to help you understand and implement the guidelines. 
You can develop and submit techniques that may be added to Techniques for 
WCAG 2.0. 
You will be ahead of some others, and when WCAG 2.0 is finalized you will 
be able to meet it sooner. 

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able