11 Feb 2009 - 4:28am
You're on the right track! What I think is happening here is that you're looking at that silly WCAG wording and thinking there's something else in there you haven't seen. It reads like a standard pre-nuptial agreement for Donald Trump, doesn't it?
The statement: "any information or functionality that is implemented in technologies that are not accessibility supported are also be available via technologies that are accessibility supported" means in practical terms that you cannot do anything in JS that you can't be done when JS is disabled or unavailable. So if you capture the submit event in such a way that *only* JS can submit the form, you're not following this statement, as I think you're probably already aware.
Now for some real-world facts:
1. WCAG "compliance" does not guarantee 'accessibility' - i.e. that everyone will be able to submit your form. Most accessibility bigwigs will agree that WCAG is flawed because it frequently (and some cases understandably) doesn't address a lot of real-world issues.
If you need specialist answers to accessibility questions, it's certainly worth visiting accessifyforum.com and/or signing up!