WebAIM - Web Accessibility In Mind

E-mail List Archives

javascript and webapps

for

From: Sam Foster
Date: Mar 21, 2006 11:30PM

Another question - not too groan-worthy I hope.

Is there any point at which a javascript-dependant application can be
deemed accessible, or are the 2 mutually exclusive? My experience says
that you want progressive enhancement - add the bells and whistles, but
add them on top of a functioning application where javascript (and css
etc.) aren't available. But.. I'm now with a team were there's been a
working assumption that requiring javascript is acceptable for an
application vs. a web page, and the cost of rebuilding to a more
progressive enhancement model may simply be too great.
What then? There's lots I can do to improve accessibility while
maintaining this assumption, and lots of assisted browsing scenarios
will work just fine with javascript. And some is surely better than none.

I've done work where accessibilty trumped all (like the AIR events), but
in a comercial environment it jostles with a host of other priorities.
We'd all like to do the right thing, but some compromise is inevitable.
Should I let the javascript thing go and focus efforts where I can, or
is this a untenable position that will land us in court (or lose
government clients) eventually??

Sam