JAWS is an app. A browser layer. To give blind people a chance there is a lot of HTML that can (and should ) be done that sighted people don't see. But it is a fudge, the best you can do,
I want options to make the experience "responsive", as the jargon has it these days.

My idea is to tell people what they can do to use the my site, and the core search engine is 150K of JavaScript (and growing) - I am not going to change that. Whatever I do has to be a layer on top of that.

Telling blind people is easier in speech. Asking them to find, is a bind. Telling them where it is in audio, is far better. They are not deaf!

They are not being asked to experiment - it will be handed them on a plate, I don't want them to stick their fingers in the mashed potato as they fumble around aiming for the ceramic bit.

And whatever I do, will still be accessed via JAWS, (Job Access With Speech).