It is unfortunate that modern web development has led to websites so complex that they either break entirely or look terrible in text-based browsers like Lynx. Take Mastodon, for example: $ lynx https://mastodon.social/ […] To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform. The C2 Wiki does not load either: $ lynx https://wiki.c2.co…
Is it really so bad? Unlike computer interfaces, the web was never text-first. It was graphical from the start. The first browser was in a GUI, not a terminal. Sites have been hobbled/broken on Lynx since the very beginning. It's neat and can be convenient to have a browser that works in your terminal for simple stuff, but the web was never designed for that. It's natural and to be expected that many sites will break…
Even back then, the book recommended testing your web site in Lynx for two reasons:
1. Web sites are supposed to gracefully degrade when viewed in browsers without support for advanced features.
2. Accessibility matters, and while most of us don't have access to or know how to operate screen readers if we can comfortably view and navigate a web site in Lynx there's a pretty decent chance that it'll be usable with a screen reader.
It's been ~30 years since then and those reasons still apply just as well. For the vast majority of web sites which do not have any need to be interactive webapps there's not really any good reason for it not to be perfectly usable in a text-only browser, and if it's both readable and navigable in a text browser it should also be with a screen reader.