Instead it's much adieu about nothing since you could simply serve a text file.
That being said, <plaintext> is a nifty historical footnote I didn't know about, so that's cool.
Side note, a lot of people aren't aware that businesses in the US can be sued for violations of the Americans with Disabilities Act (ADA) for non-accessible websites.
BTW, Shakespeare's Much Ado About Nothing was a pun on "noting" and entailed the passing of notes. I believe "nothing" was pronounced more like "noting" at the time.
and now without much ado I will say goodbye for this comment. Adieu.
https://www.telegraph.co.uk/culture/books/booknews/8313901/T...
Shakespeare often punned about such "country matters".
https://web.archive.org/web/20230719135333if_/http://no-ht.m...
Can we simply say, Javascript driven SPA was a bad fad
To name a few:
- hard-coded buttons disguised as a hyperlink
- customized textbox/dropdown disallow copy-paste
- poorly defined broken URLs and important pages without a proper URL
I can see ascii art being a nightmare for screen readers.
But since so many people do not understand the importance of HTML for accessibility, I feel the need to stress that this page may be a horrible experience for non-sighted people.
To sighted people, obscure unicode characters may look like text in a different font, but do they for screen readers? The same goes for ASCII art and the tables on this page.
Do all the fun stuff! But please draw the right conclusions for real-world projects.