1. A modern browser with JS intentionally turned off
2. An old browser
3. A specialized browser (WebTV, cell phone, etc.)
In case 1, the user has decided for themselves that they don’t want to see JS-based content (for whatever personal reason), and in cases 2 and 3, the user wouldn’t be seeing your site correctly anyway, JS or not – those browsers don’t support the latest standards.
Is it worth the time to craft JS-free fallbacks for our sites just for this specific group of people? Again, going by the stats, there are more people with screen resolutions of 800 x 600 than there are people with JS disabled, yet everyone designs their site for 1024 x 768 nowadays – even major corporations (Apple, Microsoft, Amazon, etc.).
Personally I don’t think you should require JS to perform main functions on a web application, but I do understand the nicety and some improvement on usability issues it can do.
Here’s what mostly can’t use or don’t support* JS:
Else, I’d say go for it. Make it fancy, and impress (future) clients if you can ;)
Also, if you don’t have Lynx or don’t want it, I recommend checking out the Yellowpipe Lynx Viewer-plugin for Firefox
I’ve used sites where the submit-button looks like this:
This fails and does not degrade gracefully. The page I got it from didn’t even include a <noscript>!
You must be logged in to reply to this topic.