[Skip navigation]

What Does This Mean?

Did you notice?

Each page has in its footer validity links for CSS, XHTML and Web Accesibility (WAI).

Further more, the Accessibility Features section provide useful informations for visitors with disabilities.

More to read...

The Web Standards Project

Web Standards Group

Zeldman: Designing With Web Standards

W3C QA: How to achieve Web Standards

MACCAWS: The Way Forward with Web Standards

An equal opportunity disease afflicts nearly every site now on the web, from the humblest personal home pages to the multimillion-dollar sites of corporate giants. Cunning and insidious, the disease goes largely unrecognized because it is based on industry norms. Although their owners and managers might not know it yet, 99.9% of all websites are obsolete.

These sites might look and work all right in mainstream, desktop browsers whose names end in the numbers 4 or 5. But outside these fault-tolerant environments, the symptoms of disease and decay have already started to appear.

In modern versions of Microsoft Internet Explorer, Opera Software's Opera browser, Netscape Navigator, and Mozilla (the Open Source, Gecko-based browser whose code drives Navigator, CompuServe, AOL for OS X, AOL China, and other browsing environments), carefully constructed layouts have begun falling apart and expensively engineered behaviors have stopped working. As these leading browsers evolve, site performance continues to deteriorate.

In "off-brand" browsers, in screen readers used by people with disabilities, and in increasingly popular nontraditional devices from Palm Pilots to web-enabled cell phones, many of these sites have never worked and still don't, whereas others function marginally at best. Depending on needs and budget, site owners and developers have either ignored these off-brand browsers and devices or supported them by detecting their presence and feeding them customized markup and code, just as they do for "regular" browsers.

Likewise, using XHTML and CSS need not necessitate telling Netscape 4 users to go take a hike. A site properly designed and built with standards is unlikely to look pixel-for-pixel the same in Netscape 4 as it does in more compliant browsers. In fact, depending on your design method, it might look entirely different. And that's probably okay.

Struggling to cope with ever-widening incompatibilities, designers and developers came up with the practice of authoring customized versions of (nonstandard) markup and code for each differently deficient browser that came along. It was all we could do at the time if we hoped to create sites that would work in more than one browser or operating system. It's the wrong thing to do today because modern browsers support the same open standards. Yet the practice persists, needlessly gobbling scarce resources, fragmenting the web, and leading to inaccessible and unusable sites.