How about delivering both types of content and letting the browser decide which content to display. Do a search for "noscript tags".
This is a common problem that is considered everyday by web programmers. There are also ways to make the page redirect elsewhere if the browser displays the content of the <noscript> tags, which only happens if javascript is disabled. Or, you can have the javascript redirect to a new page, so people with javascript will go to a different page. However, redirecting like that has search engine implications, which you should investigate.
I believe the accepted practice is to develop the page without js, and get it working within the scheme of your website. That is what non-js enabled users will see and use. Then you add the bells and whistles with js, which allows users with js enabled to see the extra stuff. In other words, js is not supposed to be responsible for the guts of the page--js is supposed to be used to enhance a page.
The other option for web programmers who don't care about non js users is to use <noscript> tags to say, "Sorry, this site doesn't work unless you have javascript enabled. Get lost."
|