But this will never suffice for companies that have a marketing budget. They need to promote their brand more than they need to distribute information. It's not the web's fault. And any scheme you come up with is going to suffer the same fate.
For an excellent example of the first half of this, see Mark Pilgrim's excellent "Dive into HTML5". I'm referring here to the structure of the document, not the content (though that's also excellent). The document is virtually entirely bare-bones HTML5 tags, with a typical nesting depth of 2-3 elements, rarely more.
Mark has also applied an excellent (and being the exception, proving the rule that virtually all CSS sucks) stylesheet to the site. Again with a minimum of chrome and glitter.
My thought, again, is that, similar to how LaTeX offers a few basic documenbt templates, a set of standardised site semantic layouts, for which clients offer standard presentation formats, with variants for high and low contrast, "night mode", and simplified design, might be preferable.
Am I now expected to either write, or hunt down a stylesheet for every single host?
Without the CSS, the navigation sidebar just goes at the top, which makes most sites unusable.
I'm not claiming that the user experience of individually styling each website is preferable. I am stating that the design experience of utterly nuking virtually all sites' CSS is vastly preferable to suffering through what's shoved at me.
Using Stylinsh, I can:
1. Create a default CSS which applies to all sites.
2. Create individual stylesheets matching a specific site, or regex, or domain.
3. Create one or more stylesheets which apply to multiple sites, though those have to be individually specified.
Again: I'm not claiming that the overall result is perfect or even good, simply that, for me, with reasonable CSS chops and sufficient frustration with the status quo to care and take the effort, that what I end up with is better than what I started with, and worth the (varying levels of) effort (on a per-site basis).
The more often I use/visit a site the more likely I am to change its CSS to suit my tastes. Some site I visit only once, I'll simply leave unstyled or apply "unstyled" to it (manually).
I've posted a few iterations of "unstyled" to Pastebin, one from August: http://pastebin.com/7TRnwG78
(This may not be the most recent, system on which that lives is currently unavailable.)
That said, there's a separate "annoyances" CSS (which I don't believe I've posted though you might find a copy via DDG/Google) which attacks a whole slew of other gripes: headers, footers, interstitials, modals, flyovers, etc. It's very broad (e.g., [class="modal"], [id="modal"], modal, ..., with a bunch of similar patterns for annoyances. I've got to explicitly override those on selected sites, particularly where they use confirmations and other dialogs.
Of course, the root of the problem is that HTML is not really a good basis for implementing hypermedia.
It's possible to do _very_ good things with HTML, CSS, tables, and Javascript even. I've done a few things myself of which I'm somewhat proud (my CodePen, referenced earlier in this thread, carries a few examples). But, as with much else, it's possible to throw out complete crap.
And browsers will render it. They've got multiple sets of quircks and brokenness modes to deal with just such issues.
Search engines will index that crap. Hell, many SEO optimisation techniques themselves are based on abuse of HTML (keyword and other semantics stuffing).
Tools that simply say "fuck you" and stop rendering shit content, or just do what the user actually wants, would go a large step toward fixing this. Various ReaderMode tools (now on Safari and Firefox) are a key example. I'm actually using the latest Firefox for Android and it specifically addresses a number of my own key browser grips in at least part (though by no means all or completely).
Google's Chrome is actually about the worst of browsers from this perspective, it's leaning far too much in the direction of yielding full power to Web authors. Yes, it's possible to create some slick Websites in that process, but you and up with gobs and gobs of shite.
http://deirdre.net/programming-sucks-why-i-quit/
Honestly, I miss the days when Netscape Navigator would just halt rendering in the middle of your page, saying, “No, I will not parse any more of your shit until you fix it.”
Edit: check this http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3129953/ about reiventing the wheel, a horizontal scrollbar to flip pages instead of the plain vertical scrollbar of the browser.
The NIH page suffers in that it doesn't scroll down, allowing for full-screen viewing on tablets such as the one I'm using. There's a permanently visible browser nav and tab bar on it, which I'd prefer to have go away. Many sites with persistent headers suffer similarly (e.g., G+).
The arguments I've had when higher ups want the Web page to render pixel perfect to the "design". "But all renderers are different"
I've been online since long before the World Wide Web was a thing, and I've watched the evolution of Web design from TBL's first proposals, through background wallpapers, animated flames, multicoloured layouts, spacing pixels and table-based layouts through to the saviours that were supposed to be CSS and AJAX.
It's all been a terrible mistake.
I'm leaning to a model in which a standard set of templates exist: article page, index, gallary, catalog, search -- and the client has a set of standard (or custom) templates to view them with. Client overrides server and author.
Yes, this means putting all but three Web designers in the world out of work. Couldn't happen soon enough.
A recent discovery of mine was that the combination of uMatrix and Stylish is fantastic. As the first blocks by default all CSS, fonts, and JS, I'm given a blank canvas from which I can apply my own preferred stylings (look up Edward Morbius's motherfucking Web page for a general taste). https://ello.co/dredmorbius/post/GwGDOuSqWn91CRkQBUQeYQ
Before this it was a stable of over 1800 local stylesheets, most quite brief and/or standard, to fix common gripes.
And it's not just me. A visually disabled friend, totally blind in one eye, 20/60 vision at best with correction in the other, and generally not particularly computer literate, has endless frustrations with gimmicky websites with all the usual crap: low contrast, tiny font sizes, hard-to-read fonts, poor colour choices, content which re-renders multiple times,etc.
I just spent an hour at the local Apple store exploring various accessibility options. While there are some for Mac and iOS products, they're terribly insufficient. No way to globally set user font sizes. No way to make "reader mode" the default for either Safari or Firefox. No alternative to mouse and icon interactions in far too many cases.
And that's just the OS. The Web as a whole is many times worse.
Readability Mode for the entire Web, with a small header space for branding, would be a huge improvement over the status quo.