I am not quite sure I understand. If you're really trying to use JAWS or NVDA to work with lynx on the web, you are mixing things up. There are basically two worlds for blind users: the "old" text-only terminal interfaces thing which started in the good old DOS days at least for me) and was kept alive in Linux terminal applications. And the GUI world, where you have a screen reader interact with the various elements an application is putting on-screen. In the first world, the screen reader basically just sees a grid of characters. In the second world, the screen reader needs to reconstruct a text representation from the widget info it can obtain.
In other words, if you want to work on the web, with something like NVDA as a screen reader, you want to use Firefox or some other modern browser, not lynx.
If you are like me, spending 99% of your time in tmux, lynx is a nice thing to use, but there is nothing really accessibility specific here. Lynx is just a terminal application. And if you are a skilled blind user used to dealing with plain-text grid-stuff, you can use it just fine for whatever it still works for...
In other words, if you want to work on the web, with something like NVDA as a screen reader, you want to use Firefox or some other modern browser, not lynx.
If you are like me, spending 99% of your time in tmux, lynx is a nice thing to use, but there is nothing really accessibility specific here. Lynx is just a terminal application. And if you are a skilled blind user used to dealing with plain-text grid-stuff, you can use it just fine for whatever it still works for...