Not an accessibility issue
Make the decision based on facts
@vick08 asked his followers:
- A somewhat local newspaper site….92 JS files, 1.5 megs, onload fires 1 minute 3 seconds.
- I turn off JS when I’m going to what I believe might be a dicey site, since that the vector for most malicious software.
It’s out of your control
Gawker/Lifehacker have violated the principle of progressive enhancement, and they paid for it immediately with an extended outage on day one of their new site launch.
isolani – Breaking the Web with hash-bangs
console.log() left in by your developers (this causes scripts to fail if Firebug, or similar, is not enabled in the browser).
How should pages be developed?
Always develop with progressive enhancement in mind, by thinking about your coding in layers:
- Start with plain, well-structured HTML to display all your content, ie all forms should submit, ensure all links can be followed.