[shocks]

You are a minority. Perhaps not here (HN) because "I disable Javascript" seems to be a pretty trendy thing to say (:P), but in the world at large you are.

It's bad enough we have to build websites that work on IE8. We have to worry about screen readers and other accessibility problems, but we also have to worry about a fraction of users that disable a fundamental browser feature literally every site uses? Nah. It'll break and you can expect it to break! Sorry. :)

[oneeyedpigeon]

You don't really have to 'worry' about those things, you just follow best practices and - for the most part - they get dealt with automatically. Following the standards always gets you additional benefits that the "javascript required" crowd always gloss over. As a trivial example (there are many more), using a non-existent fragment identifier as a link target and capturing the click event doesn't just break when javascript is unavailable, it also breaks opening that link in a new tab.

[adrusi]

You have to make your site accessible to search engines, so as long as you're not doing something weird like using javascript for styling and layout, just treating users who have disabled javascript as search engines should work just fine.

[bsimpson]

Google has been working pretty aggressively at learning to crawl JS-framework-powered apps lately. I'd still play it safe and serve up HTML when possible, but JS isn't the SEO black hole it once was.

[thrownaway122]

For text and images and videos (which is what a webpage is for after all) if one sticks to a simple html and simple set of css do you need to worry about all those issues? Or do they just go away? e.g could a simple html version served to e.g. screen-reader using users also work for non-javascript using users?

>literally every site uses

Ironic that you would post that on a site that works without it...