Question

Site markup is targeted to HTML5. So it’s assumed to be runned in modern browsers. Does it make any sense to support javascript disabled scenarios?

If it does, how flexible it should be? Should it allow users to do all or just basic things?

And the same question for CSS. Should I use some patterns (e.g. tables instead of divs and so on) to support clients with disabled CSS?

P.S. I don’t have any specific requirements, so it’s like a personal challenge.

Answer 1

Its up to you on supporting no javascript. Why don’t you ask yourself these questions first?

• Do I want my site to be used by blind people (who often use browsers which don’t play well with javascript)?
• Is this for a federal/gov’t agency? (Often, gov’t agencies REQUIRE this in order to accommodate people from the first item)
• Do I want to accommodate all of the security nuts (no insult intended) and people who turn javascript off to avoid annoying ads?

You should ask yourself these questions first. I’m not trying to suggest you don’t like blind people or you’re lazy. I know, that if you already have a site which doesn’t support javascript turned off, this is going to be a nightmare. So I’m not trying to fling insults/guilt trips. But if you’re starting from scratch, then IMHO, it is a good idea to build it without javascript, and then go back and add it in later.

As far as CSS being disabled, I think you’re ok not worrying about that one.

As far as divs vs tables. Go with divs, and use tables if you’re rendering tabular data. Basically, if you’re trying to make something render in a certain place, and you’re trying to use a table, you’re doing it wrong (you can google about it if you’re that interested).