Web Development Best Practices - How to Support Javascript Disabled

Question

What is the best thing to do when a user doesn't have JavaScript enabled? What is the best way to deliver content to that kind of user? What is the best way to keep a site readable by search engines?

I can think of two ways to achieve this, but do not know what is better (or if a 3rd option is better):

1. Rely on the meta-refresh tag to redirect users to a non-javascript version of site. Wrap the meta-refresh tag in a noscript tag so it will be ignored by those with javascript.
2. Rely on an iframe tag located within the body tag to deliver a non-javascript version of site. Wrap the iframe tag in a a noscript tag so it will be ignored by those with javascript.

I would also appreciate high-profile examples of the correct or incorrect way to do this.

--------- ADDITION TO QUESTION -----------

Here is an example of what I have done in the past to address this: http://photocontest.highpoint.edu/

I want to make sure there aren't better ways to do this.

Rugby

If you're coding for JavaScript then thinking about what to do without it, you're doing it wrong. – Michal

The best way would be progressive enhancement. Or you ignore non-JavaScript users. – Zephaniah

and graceful degradation – Qualm

I haven't written any code yet for this project. Just trying to come up with best plan before I start. I have to support non-JavaScript users with this project (search engine indexing). – Rugby

The first question I'd ask is who are your target users, are they likely to be using screen readers or mobile devices without javascript etc. etc. – Sara

@Sara I need to have site indexable by search engines (top priority). Other reasons for non-Javascript support are valid, too, but a lower priority. – Rugby

Answer 1

You are talking about graceful degradation: Designing and making the site to work with javascript, then making the site still work with javascript turned off. The easiest thing to do is include the html "noscript" tag somewhere near the top of your page that gives a message saying that the site REQUIRES javascript or things won't work right. SO is a perfect example of this. Most of the buttons at the top of the screen run via javascript. Turn it off and you get a nice red banner and the drop down js effects are gone.

I prefer progressive enhancement development. Get the site working in it's entirety without javascript / flash / css3 / whatever, THEN enhance it bit by bit (still include the noscript tag) to improve the user experience. This ensures you have a fully working, readable website regardless if you're a disabled user with a screen reader or search engine, whilst providing a good user experience for users with newer browsers.

Bottom line: for any dynamically generated content (for example page elements generated via AJAX) there has to be a static page alternative where this content must be available via a standard link. If you are using javascript for tabbed content, then show all the content in a way that is consistent with the rest of the webpage.

An example is http://www.bbc.co.uk/news/ Turn off javascript and you have a full page of written content, pictures, links etc. Turn on javascript and you get scrolling news stories, tabbed content, scrolling pictures and so on.

I'm going to be naughty and post links to wikipedia:

Progressive Enhancement

Graceful Degredation

Roughdry

Thank you for a real-world example. – Rugby

Answer 2

You have another option, just load the same page but make it work for noscript users (progressive enhancement/gracefull degradation).

A simple example: You want to load content into a div with ajax, make an <a> tag linking to the full page with the new content (noscript behavior) and bind the <a> tag with jQuery to intercept clicks and load with ajax (script behavior).

$('a.ajax').click(function(){
var anchor = $(this);
$('#content').load(anchor.attr('href') + ' #content');
return false;
});

Qualm

Answer 3

I'm not entirely sure if Progressive Enhancement is considered to be best practice these days but it's the approach I personally favour. In this case you write your server side code so that it functions like a standard web 1.0 web app (no JavaScript) to provide at least enough functionality for the system to work without JavaScript. You then start layering JavaScript functionality on top of this to make the system more user friendly. If done properly you should end up with a web app that at least provides enough functionality to be useful for non-JavaScript users.

A related process is known as Graceful Degradation, which works in a similar way but starts with the assumption that a user has JavaScript enabled and build in workarounds for cases where they don/t. This has a drawback, however, in that if you overlook something you can leave a non-JavaScript user without a fallback.

Progressive Enhancement example for a search page: Build your search page so that it normally just returns a HTML page of search results, but also add a flag that can be set via GET that when set, it returns XML or JSON instead. On the search page, include a script that does an AJAX request to the search page with the flag appended onto the query string and then replaces the main content of the page with the result of the AJAX call. JavaScript users get the benefit of AJAX but those without JavaScript still get a workable search page.

http://en.wikipedia.org/wiki/Progressive_enhancement

Hooper

Answer 4

If your application must have javascript to function then there's nothing you can do except show them a polite message in a noscript tag.

Otherwise, you should be thinking the other way around.

1. Build your site without JS
2. Give awesome user experience and make it full functional
3. Add JS and make the UX even more functional. Layer the JS on top.

So if the user doesn't have JS, your site will still revert to step two of your site state.

As for crawling. If your site depends on AJAX and a lot of JS to work, you can make gogole aware of it : http://code.google.com/web/ajaxcrawling/docs/getting-started.html

Micky

Thank you! That Google Ajax site crawl guide will be helpful. – Rugby

Answer 5

One quick tip that may help you: just install lynx, a command-line web browser, and you'll immediately see how google and other seo see your site (and blind people too). This is very useful. Of course, in a command line windows, there's no graphics and javascript is disabled.

Beware

Answer 6

If you're doing "serious" Ajax (e.g. client side-routing) the following technique could be useful:

1. Use Urls without GET/"?"-parameters (it makes your life easier later on)
2. Use http://baseurl.com/#!/path/to/resource for client side-routing
3. Implement rendering of non-script HTML-version of your site (HTML snapshot is what Google calls it) at http://baseurl.com/path/to/resource
4. Wrap the whole content of your HTML snapshot in noscript-tags and redirect via top.location.href to the full version of the site
5. Handle http://baseurl.com/?_escaped_fragment=/path/to/resource - it should redirect via 301-response to http://baseurl.com/path/to/resource
6. Use a-tags only for GET-links, use forms for POST/PUT/DELETE-links - unstyle the hell out of them if necessary

A nice example code for links I found while researching "How to write proper Ajax-code":

<a href="/path/to/resource" onclick="Routing.navigate(&quot;/path/to/resource&quot;); return false;">Resource</a>

This is of course a pretty complex solution but it should enable both SEO (including non-search engine crawlers) and accessibility. The problem is that you have to be able to render your page server- AND client side.

One solution could be to use a templating framework like mustache where implementations for different platforms exist.

1. Use something like {{#pagelet}}/path/to/partial{{/pagelet}} for dynamic parts of your page - example: {{#pagelet}}/image/{{image_id}}/preview{{/pagelet}}
2. In your client-side rendering, pagelet would be implemented to be dynamically replaced with something loaded via Ajax (for example: render )
3. In your server-side rendering, pagelet would just be rendered directly (in doubt just curl the pagelet and render it right away - or if you can write the code asynchronously do it just as you would do it client side: write some temporary span into a buffer, start fetching all the pagelets, replace the temporary spans as the pagelets arrive and flush the buffer once all pagelets have been rendered.

That's the best general design I found so far. You can deep link into your app, it's search engine friendly and it should force you to build a page that gracefully degrades.

P.S.: One advantage of the techniques described above is that both the Ajax- and the "Web 1.0"-rendering of a page could profit from memcached-caching of whole pagelets.

Resinate

Answer 7

I would prefer to code the page without javascript and then if javascript is enabled, we redirect users to a similar page with javascript. (same concept as progressive enhancement)

redirecting with javascript

Exarate