Two months ago I got into an argument with TR on the quality of Microsoft Powerpoint; today I got into an argument with Truman on the quality of web-pages and the intellect of their designers. I suppose I have a short fuse when it comes to software quality, layout and usability issues.
On the first occasion, it was totally off-topic, but at least it was TR’s own blog and it was he who introduced the powerpoint motif; but this time, though it was not entirely off-topic, it was a third person’s blog (Dilip’s) which makes it much less excusable. So I may as well put down what I think about the whole thing, and in future link to it rather than arguing. (Of course, many others have written similar things, and I will link to some of them below.) In this post I’ll focus on the web, and webpages; in a later post I’ll talk about Microsoft’s products. But in both cases a key point is emphasising standards versus emphasising proprietary (and expensive) products.
We take standards for granted everywhere in daily life: my Sony CDs of Miles Davis will play on my Onkyo player, or someone else’s Philips player, or on a laptop, without problem. That’s because audio CDs adhere to the red book standard. Similarly, you can fill your car with petrol at any of a dozen pumps: the formulation is standard (we ignore the adulteration problem here) and a manufacturer of cars that insisted on its own particular formulation would not get a huge market. (This is also why alternative fuels like CNG find it hard to break in.)
In computer information too, many things are standard, like plain text files (created with the ASCII character set) or MP3 audio files. Specifications exist for these, and readers/players must conform to these specifications, or they don’t work.
What happens if you create a document, or a CD or a petrol formulation, that deviates from the specifications? In mild cases you may just get degraded performance (eg, the document displays with errors, the CD may play partially, the car may run with poor mileage); in extreme cases the product is unusable.
For interoperability, then, adherence to standards is essential. So why does it happen so often that “this web page looks funny”?
The language of the web is HTML, or “hypertext markup language”. The specifications of HTML are maintained by a consortium called the World Wide Web Consortium, whose members include Microsoft, the Mozilla Foundation, Opera Software, and pretty much any other web-related company you can think of. There are now several versions of HTML (and its successor, XHTML), each with its own specification. The consortium hosts a validator to help you check the correctness of your webpage. Mozilla’s webpage passes, as does Opera’s; while Microsoft’s has five errors, which is really quite respectable. Most web pages report dozens of errors. In fact, you’d have a hard time finding sites, other than the above two and W3C’s own pages, that pass the validator.
Why is practically every page on the internet invalid HTML? There are several reasons:
- If you write a syntactically incorrect C program, it will not compile. By contrast, if you write a syntactically incorrect HTML file, most browsers will attempt to display it anyway. If the results look good enough, most web developers won’t care that it is wrong. This leads to the “slow degradation” problem I mentioned above: strict syntax-checking would have avoided it.
- Most people no longer write HTML by hand: they use programs like Microsoft Frontpage. These, too, don’t care about errors as long as it looks OK to a browser (and often, to a specific browser, typically Microsoft Internet Explorer).
- Back in the early days of the web, there were very few browsers around; the first to achieve some popularity was NCSA Mosaic, but it was quickly supplanted by Netscape Navigator. Netscape, knowing it had a market lead and wanting to retain it, extended HTML in various ways without the consortium’s approval, and encouraged developers to use its extensions (which its HTML authoring program also produced). Later, Microsoft strong-armed itself into the market lead and followed the same tactics. Meanwhile, neither company paid too much attention to actually following the W3C’s recommendations. The result was a mishmash of standards — the W3C’s (which nobody fully supported), Netscape’s, and Microsoft’s — and most developers (the ones who cared) just threw up their hands and supported the two most popular browsers, and eventually, just Microsoft’s.
Today, the browser situation, at least, is much better: at least three major browsers — Mozilla, Safari/Konqueror, Opera — are largely standards-compliant, and the new Internet Explorer 7 is a big improvement over its predecessors. Nevertheless, most webpages out there don’t support the standards.
Standards-compliant webpages tend to display properly across all browsers. With many webpages, that is not the case. But it is hard to blame web designers too much when the major browser vendors were so slow to the table. Unfortunately, there is much else that the designers — and also the writers of web-authoring software — can be blamed for.
Web authoring is not typesetting!
Printing a book, and creating a webpage, have this in common: they involve displaying text and graphics on a medium (a monitor, or paper). But there the similarities end.
While the book’s layout is in the hands of the creator, the webpage’s layout is in the hands of the web browser on the user’s computer. For this reason, HTML is a “markup language”, not a typesetting language: it describes the attributes of various text objects but does not prescribe (except at a crude level) where on the page the text should go. This is important: displays come in various sizes and resolutions, from tiny mobile-phone screens to 2048×1536 monstrosities (and beyond), and a one-size-fits-all approach will not work. Moreover, high-quality serif fonts may be suitable for the hi-res displays, while a simple but readable sans-serif font would be more appropriate for the mobile phone. So one should not specify, or make assumptions, on such things as font families and font sizes.
Unfortunately, lots of pages do make such assumptions. For example, suppose I have poor eyesight and choose an unusually large font size. Wikipedia (which passes the validator) looks cluttered, because of its multi-column format, but the elements are still correctly positioned:
However, the home page of FreeBSD (a Unix-like operating system), which also validates, is a disaster when viewed at large font sizes:
Needless to say, pages that don’t validate fare even worse. Try it (on Mozilla Firefox, Ctrl-+ increases the font size).
The Any Browser campaign has more information on how to make a web page look good on any browser, and how to make it “degrade gracefully” when assumed features aren’t present in a browser.
The biggest misfeature to be a part of the web standard is probably frames. Rather than holding forth, I’ll just link to what Jakob Nielsen says about them. (Nielsen’s 1996 list of web-design mistakes is still worth reading, as are many of his later writings.)
Another misfeature is pop-up windows. Enough said. (It is never necessary to open a new window: the user can choose to do that when he/she wants to.)
So far I have talked about HTML. But a lot of web pages have chosen to avoid HTML altogether, and put together their entire website in Flash. There are several things wrong with this, such as:
- Web browsers are available on nearly every platform; flash plugins are unavailable on most platforms, including all 64-bit systems (even 64-bit Windows-XP).
- One can cut-and-paste, search, index, link to HTML pages. One can’t do that with flash pages.
- The visually impaired can resize the text on HTML pages, or use a reader. With flash they’re out of luck.
- The download is just so much bigger with flash. Many people still use dial-up internet connections.
My other peeves with web design relate to usability (where links are placed, what they do, how you access them) and layout (a subject that overlaps with what I plan to say about Microsoft Word and Powerpoint); having expended sufficient verbiage for an evening, I will return to these topics later.
Dilip (correctly) pulled me up for suggesting that all web designers are idiots. The above observations suggest that to a large extent, they are more sinned against than sinning: if authoring software, and (till recently) browsers, do not satisfy standards, what are they to do?
Nevertheless, I do not absolve them of responsibility. Today, web browsers do follow standards, and it should be easy to ensure a webpage works on them. Moreover, Mozilla Firefox and Opera can both be installed easily on Windows machines (Safari can’t, but its parent, Konqueror, can be installed under a unix-like environment called CygWin). Mozilla Firefox alone commands over 10% of the market, and the non-Microsoft browsers put together approach (or perhaps exceed) 20%. These browsers also allow easy scaling of fonts and setting of font-family and font-size preferences. It is, if not idiotic, at least completely irresponsible to choose to test only on one web browser, MS IE, and that too only on version 6. With the release of (and, often, enforced upgrade to) IE7, many sites are now broken and need to be fixed; they need never have been broken in the first place.