You didn't answer my question. You stated that using JavaScript in a menu
would affect accessibility. I asked you to be specific about how
Accessibility would be affected. If you want to be believed, you have to
provide some evidence that supports what you say. "Accessibility" is a
term with a meaning. The W3C has written a lot about it. Have you read any
of it?
Yes. Quite a bit, in fact.
I'm not sure why it's so hard to understand that javascript-based navigation
is inaccessible to anyone without javascript.
JIMCO mentioned Adaptive Rendering. I haven't played with that, but will
take a look at it (not sure how it handles postbacks, though without
javascript...)
You'll note that the W3C doesn't seem to think that JavaScript is bad for
accessibility. Instead, they have published guidelines about how to use it
in ways that do not harm accessibility.
And relying solely on javascript for navigation certainly harms
accessibility.
Also, there's a large difference between the technical recommendations and
actual implementation of accessibility (and usability, for that matter)
issue.
Ie, being bobby-validated doesn't necessarily mean your site is actually
accessible to a person.
After reading through that, come on back and tell me again how JavaScript
will affect accessibility in a menu, and specifically, in the ASP.Net Menu
Control.
Does the ASP.net menu control generate javascript-based postback triggers
for navigation? If so, does it do it unobtrusively or will the menu not work
if one doesn't have javascript?
We haven't upgraded to .net 2.0 so haven't taken a look at this control in
detail yet. MS may very well have made accessibility improvements to their
controls. I'd love to see one of these controls in actual use on a site. Do
you know of any examples?
-Darrel