Ironically, it's impossible to read this ACLU page without enabling Javascript, which opens one up to more browser fingerprinting attacks, potential Javascript vulenrabilities, and tracking.
Google, the most popular page on the internet, doesn't force you to use Javascript.
About 3 months ago Google became unusable when browsed through w3m: search results are not rendered as links, just as a regular text that can't be followed-through. They clearly assume you always browse with js enabled, I can't think of any other explanation.
Actually, I just tried it on w3m. Still works just fine. It must be that whoever compiled your w3m messed up in some way.
As for reproducability, in just this week I've seen two versions of image search page back and forth, with little visual changes here and there as well as CORS headers that break some bookmarklets that I occasionally use. I guess they're doing some A/B testing, or just roll out changes slowly.
Discussed here, with a link to full parameters:
Take a look at the parameter list in the linked page. There's no "fd" in there.
I've edited my comment in this thread, posted a reply to the earlier one.