Bray on browsers and standards support
Tim Bray has posted an excellent essay on the state of Web browsers, which encompasses Netscape dropping browser development and Microsoft stopping stand alone browser development (development seemingly only for users MSN and their next Operating System, which is due out in mid-2005 at the earliest).
Tim points out users do have a choice in the browsers they choose, and will be better off selecting a non-Microsoft browser. Tim quotes Peter-Paul Koch:
[Microsoft Internet] Explorer cannot support today's technology, or even yesterday's, because of the limitations of its code engine. So it moves towards the position Netscape 4 once held: the most serious liability in Web design and a prospective loser.
This is becoming a well understood assessment from Web designers and application developers that use browsers for their presentation layer. Developers that have tried moving to XHTML with table-less layout using CSS get the IE headaches, which are very similar to Netscape 4 migraines. This environment of poor standards compliance is a world many Web developers and application developers have been watching erode as the rest of the modern browser development firms have moved to working toward the only Web standard for HTML markup.
Companies that develop applications that can output solid standards compliant (X)HTML are at the forefront of their fields (see Quark). The creators of content understand the need not only create a print version, but also digitally accessible versions. This means that valid HTML or XHTML is one version. The U.S Department of Justice, in its Accessibility of State and Local Government Websites to People with Disabilities report advises:
When posting documents on the website, always provide them in HTML or a text-based format (even if you are also providing them in another format, such as Portable Document Format (PDF)).
The reason is that HTML can be marked-up to provide information to various applications that can be used by those that are disabled. The site readers that read (X)HTML content audibly for those with visual disabilities (or those having their news read to them as they drive) base their tools on the same Web standards most Web developers have been moving to the past few years. Not only to the disabled benefit, but so do those with mobile devices as most of the mobile devices are now employing browsers that comprehend standards compliant (X)HTML. There is no need to waste money on applications that create content for varied devices by repurposing the content and applying a new presentation layer. In the digital world (X)HTML can be the one presentation layer that fits all. It is that now.