I get that you’re demonstrating how a simple page enables simple tools for reading it.
But, to avoid any misconceptions, it’s been many years since blind people have used specialized browsers, built from the ground up for blind people, to read web pages. We mostly use mainstream browsers together with screen readers now. And even the old specialized browsers were more advanced than the Unix pipeline you gave; they properly parsed HTML and let the user move around the page and interactively read parts of it.
And your pipeline has some problems even for a simple page like this one. Notice that the ’ entities were unhandled.
More like I don’t trust myself to be even close to as good.
curl https://sourcehut.org/blog/2020-05-27-accessibility-through-simplicity/ | tr '\n' ' ' | sed 's/<[^>]*>//g; s/ //g; s/&..quot;/"/g; s/</</g; s/>/>/g; s/ */ /g' | xargs -0 espeak -w 2020-05-27-accessibility-through-simplicity.wavhttp://josuah.net/tmp/2020-05-27-accessibility-through-simplicity.wav
I get that you’re demonstrating how a simple page enables simple tools for reading it.
But, to avoid any misconceptions, it’s been many years since blind people have used specialized browsers, built from the ground up for blind people, to read web pages. We mostly use mainstream browsers together with screen readers now. And even the old specialized browsers were more advanced than the Unix pipeline you gave; they properly parsed HTML and let the user move around the page and interactively read parts of it.
And your pipeline has some problems even for a simple page like this one. Notice that the
’entities were unhandled.’(assumed&rsquot;)<em>,<code>,<li>, …Hmm… we’ll see again about using that pipeline for anything beyond a flawed proof of concept.
Is edbrowse one of them?