With the ubiquity of ajax and js fancification of the web, the likelihood of a user turning off javascript is low. My workaround was to transform a semantically elegant class declaration (from a designer's perspective), to a semantically elegant id declaration (from an information architect's perspective). Designers don't give a hoot what the div is called as long as it looks good.
What I'd really like to see is a way to pull off the jQuery workaround inside CSS itself. Something like: div#head { apply: [classname] }, where you an array of predefined classes to define the style. I did a little reconnaissance on this topic, but no luck. :(
It's funny because I just created a semantic layout generator for Blueprint that is a lot alike in its implementation. You pass the IDs into a method and then layout your page. It'll spit out the CSS that you need so that you don't have to add classes in your HTML. There's a full writeup with links to the code and a how-to on Bajooter [1].
"Javascript is requesied for this site"
This screen should show after your flash into (which *doesn't* have a 'skip into' button (<-- apparently one of the most clicked links on the web))
:D
What I'd really like to see is a way to pull off the jQuery workaround inside CSS itself. Something like: div#head { apply: [classname] }, where you an array of predefined classes to define the style. I did a little reconnaissance on this topic, but no luck. :(
1. http://bajooter.com/archives/blueprint-css-archite...