I'm an insensitive clod, I hadn't thought of literotica.
I quote from CaptQuark:
It takes some extra work to produce a visually appealing page that a screen reader can easily read and navigate after the style sheets are ignored by Jaws. It requires careful planning to design a page with multiple columns (menu column on the left, main content in the middle, additional information on the right) and organizing it so a screen reader can skip to the main content without listening to menu choice after menu choice on every page but still looks appealing to sighted users after the style sheets are applied.
This is an example of what you are not supposed to do. Windows 8 makes an easy example, convolving the needs of different UI paradigms is poor design. Proper application ADA support uses two interfaces, one for the sighted, and another for the blind, designed specifically for use by a text reader. Vi and Emacs do not require such bifurcation, but these are exceptions that prove the point; nobody in their right mind would release these applications to the general public and call them user-friendly.
Customers with ADA requirements never want to pay for including a blind tester, or doing the application architecture properly for text readers. I can and do use W3C guidelines, but I'm no expert and know I'm probably doing it poorly since there's nobody to push back to tell me what I've done right or wrong. I've seen bids double and triple when the ADA requirement is a hard one that will be independently tested. Including good support for the blind in applications is expensive, which is why I thought it might be nice to look at alternatives.