I just tested changing user agents in Chrome - setting UA to a random string like "fff" gets a search page, but setting it to "Links" or "Lynx" gets "Your browser isn't supported anymore" - which is to say, this doesn't look accidental, but more like these UAs are specifically being blocked.

EDIT: Forging user agent in Links (with links -http.fake-user-agent) gets a usable homepage, but the results page just sends you to a turn-on-your-javascript page.

Try http://frogfind.com/

Seems like elinks is affected too...bummer!

I wonder to what extent visually disabled internet users are affected by this, since I can imagine at least some of them using lynx with an on-screen reader for a terminal emulator.

maybe this is a knee-jerk reaction but I don't see any good reason for this. At it's core Google's job is to take an input and list outputs. The marketshare of people using lynx is small enough that whatever advertising or ai extras they want to squeeze in won't be meaningfully impacted by not working on lynx.

Edit: corrected spelling error

Related discussion earlier this year:

Google begins requiring JavaScript for Google Search

https://news.ycombinator.com/item?id=42747092

Suggest changing title to something along lines of "Tell HN: Accessing google in lynx now shows unsupported"

Maybe, like in 2019 when a similar submission got traction, you'll be able to get it restored.

(I am no longer able to use Google with Lynx https://news.ycombinator.com/item?id=21626995)

Is Google exempted from the ADA?