Twice in the last five minutes my @privacybrowser has run into websites displaying a banner "This site works best with #Javascript enabled." Of course, the sites didn't work AT ALL with Javascript deactivated.

Ironically, one site had been redone by a firm specializing in #Accessibilty for conformance with #AODA (Accessibility for Ontarians with Disabilities Act) and #WCAG standards. You'd think they'd use language like "activated" and "deactivated" for software instead of "en/disabled".

@bobjonkman This is my personal favorite.
@bobjonkman I love it because it is so obviously not true, but Google wants it to be true.
@bobjonkman Something like Google Maps definitely works better with JavaScript (or as a native app). But that doesn’t mean it is worth the security and privacy tradeoff.

@privacybrowser

And the sadness is, Google Maps used to work fine without #Javascript.

I think most web developers (especially Google) have the smarts to build pages that build gracefully depending on browser capability: Showing content first, then style, and finally adding behaviour with Javascript. Content and style is the easy part, make sure it's there first.

So why don't they? Do the client specs require #Javascrippled content so they'll get surveillance?

(Added some #AltText, BTW)