3 ms·
If your page is unreadable with NoScript and RequestPolicy turned up to maximum paranoia, your webpage is broken. Building a broken web page is fine if you cho
by onion2k 12y ago
If your page is unreadable with NoScript and RequestPolicy turned up to maximum paranoia, your webpage is broken.
Building a broken web page is fine if you choose to build it that way. If 1% of people can't see your site, or 10%, or even 99%, then that's your choice as a developer. If I want my business website built with WebGL, asm.js, HTML5 audio and WebRTC then that's ok. I'm allowed to do that even if you can't render it. As a user you have no implicit right to use a given website if your choice to turn something off or to use a browser that doesn't support something means it won't work for you. To draw an offline analogy, I have no right to build an application if I choose to remove make from my computer.
There are exceptions - users who need special access technology like screen readers should be protected from developers who build in ways that mean they're put at a disadvantage for example - but ordinary people who choose not to use something like js have no such protections. Using a screen reader is usually not a choice.