oh come on.
It's 2015, not 1999. If you don't have javascript enabled, do you honestly expect to be able to read half of the internet?
It's 2015, not 1999. If you don't have javascript enabled, do you honestly expect to be able to read half of the internet?
As such, when the only reason that a site requires JS to be readable is sloppy coding, yes, I call them out on it.
I enable JS only for things that require it for a good reason, and where I am reasonably sure that they won't be exploited. Doing a fancy fade-in on load (which, by the way, can easily be done accessibly) is not a good reason, and I am not reasonably sure that some random blog won't be exploited.
Yes.
Yes, I expect to be able to read data without having to execute code.
And, FWIW, the Internet was pretty great in 1999. In many ways (but not all, of course) it was better than what we're stuck with now.
That gives you 16 years to learn how to make a simple, efficient, portable web page.
It's sad that Chromium doesn't have a way to disable CSS on a per-domain basis (and browser extensions are potential backdoors so I'm not going to install them).
...