I think some practical solutions could come via adding features, not taking away, in a way that brought most people into the "needs special help" category. For

I think some practical solutions could come via adding features, not taking away, in a way that brought most people into the "needs special help" category. For example, I'd like to be able to "read" interesting web pages when I'm out running or grocery shopping, as if listening to a podcast. Instead of "mobile first", if we went even further and built "screenless first", we could start with page design that was carefully built with sequential text sections, hierarchical landmarks, and standard voice controls that everyone could navigate in a fairly standard way. ("list main sections...stop. section 2, list items...stop. item 3, 150% speed...stop. next item...skip. next item...") Web devs could specially mark certain items with a keyword for direct access, but users could do it themselves with keyword macros for their favorite sites, so pretty soon a word or two takes you to a favorite site and does what you want, while you shop for pickles. Of course, this would need to be a web standard, so devs only had one target and users only had to learn it once for all audio browsers and all sites built for it. Building at least certain categories of sites to support screenless access for the general public would make the marginal cost of making it accessible (in certain ways) free. Then you add your CSS to the screenless code.