I followed the link to the article to read it.<p>And then I did what I usually do these days:  I hit the &quot;Reader Mode&quot; icon on my Firefox (Android) browser.  I do the same for most desktop sites as well.<p>Why?<p>Font too small. Contrast too low.  Line lengths too long.<p>I get <i>a better</i>, and far more importantly, <i>uniform</i> experience <i>when I bin all Web design and go with a built-in default page presentation mode.</i><p>Oh, and that <i>on a Web designer&#x27;s own blog.</i><p>Where, I presume, she doesn&#x27;t have the problem of getting idiotic client requests which violate numerous sane design concepts.<p>I&#x27;ve been saying this for some years now:  Web design isn&#x27;t the solution, <i>Web design is the problem</i>.<p>It&#x27;s going to be solved, <i>is</i> being solved, <i>in the browser</i>, by:<p>1. Stripping out extraneous crud.  I haven&#x27;t mentioned my all-but-blind friend&#x27;s difficulties in navigating anything on a computer, but extraneous crud and Shit That Randomly Changes (even the Firefox card previews on his browser start page) are huge hurdles.<p>2. Uniform presentation.<p>3. Metadata.<p>4. Curation.<p>There was a post on HN recently about ePub.  Quite frankly, an ePub based browsing &#x2F; curation tool with uniform, sane, presentation would replace about 99.99964% of my Web browsing needs.  There are a small number of missing factors from HTML, largely footnotes, equations support, and hierarchical comments&#x2F;follow-ups.  But add those and we can ditch the entire current mess for 1) ePub articles and 2) Web-deployed apps for the very small handful of sites which honestly need them.