+1 , JS is standard, allthough not everyone would agree with that.Making things work for JS disabled is just like still making your website completely work in explorer 6. Sometimes you gotta let go and move forward.
There’s a few minimum standards that all websites should adhere to: one of them is displaying content using markup so that it’s accessible to the widest amount of people as possible. Those people may be using modern browsers, older browsers, smartphones or tablets and they may even be using screen-readers for accessibility or other similar tools. You don’t have to make your content look or work the same on older browsers, but it should at least be accessible.
Sites that require JS to render content cause masisve problems for many users as they make it very hard for enabling technologies to understand how a page is structured, where the content is, etc. And as others have pointed out, it makes it hard to bookmark content or create any decent SEO opportunities. Yes, there are technical solutions to some of these issues, but if you’ve constructed a proper web page in the first place, you shouldn’t need extra functionality to make it accessible.
Look at Twitter: They converted their entire site over to a JS model for user pages using hashbangs (#!) in the URL. This broke all sorts of things for many different types of users. After a massive outcry they rrealised they’d made a big mistake, and reverted back to simpler techniques that did not rely on JS. (Their site still doesn’t fully work without JS, but that’s a story for another day… )
You should make every effort to have real content fallbacks on your site. If you’re building sites that have no content when JS is off, then you might want to consider changing your development approach.
I’m a designer/developer with 20 years experience (although I don’t currently sell anything on TF).
In the future I would hope that Envato re-consider their approval process for templates that don’t meet basic web standards.