JavaScript has always been the predominant client-side scripting language of the Internet. However, content should never be restricted by JavaScript as many users will be accessing your content via browsers without JavaScript (whether the JavaScript is disabled or not available). The graph below shows the percentage of users accessing the Internet without JavaScript over the last five years.
While it is now becoming commonplace to see extensive client-side programming users without JavaScript should not be overlooked. The W3C WAI Guidelines states:
“Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.
If this is not possible, provide equivalent information on an alternative accessible page.”
Personally, I am not in favour of ever creating two versions of the same page as keeping the two in sync often becomes a task in itself, and a rather unnecessary one at that. What I believe the W3C to be advocating is that the page content be delivered such a way that it can be viewed with or without JavaScript, i.e. delivered in non-JavaScript friendly format which is then acted upon by client-side JavaScript. If this approach is used both camps will be kept happy and the website will be accessible by all.
