Discussion Locked

To be or not to be? HTML3.2

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Is it still necesary to write web pages to conform to HTML3.2 as well as HTML4.0? Who out there is still only able to view pages written for HTML3.2? (and why!)

9 replies

by pxttocyob

The less browsers you program for the less visitors you will get. Many schools use older computers.

by andrew

You have to balance ease of design against widest possible audience. If you feel that there are enough people using 4.0 compatible browsers to make your site worthwhile, then go for it.

Here are some rough browser usage stats I dug up on the web:

3% - non-compatible (not IE or Netscape)
10% - unknown
20% - 2.0 browsers
55% - 3.0 browsers

Check out this site for some detailed browser info:

http://www.cen.uiuc.edu/bstats/latest.html

As to WHY people would choose to use an older browser...who knows!

by andrew

The stats are from this article:
http://html.about.com/library/weekly/aa111797.htm?iam=dpile&terms=%2Bbrowser+%2Bversion+%2Bhtml+%2Bstatistics

But I apologize for not noticing the date is 1998! That's what you get for a 2 min. search...

I disagree with Mr. Eckles, however, about coding to the lowest common denominator. If we did this everywhere, we'd still be writing 16 bit DOS apps. I'd rather drive the technology forward by applying the latest and greatest, while maintaining an adequate audience. If some guy tells his neighbor that he gets a better web experience from IE 5.5 over Netscape [v.whatever], then that propagates the better browser, and eventually raising the quality for everyone.

My 2?

by ian boothby

I agree with Andrew that we should try to coerce people into using newer programs, but what about those using a

by jay eckles

First of all, I'm wondering where those browser statistics came from, because they do not match the statistics I see on my site at all.

Second, a great resource for questions like this is news:comp.infosystems.www.authoring.html.

Now, my answer: It doesn't matter what browsers your visitors are using. You should be writing valid HTML code to ensure that the code can be seen by everyone!

Use HTML 4.0. It is designed to be backwards-compatible with older version of HTML. The whole point of HTML, really, is that if a browser does not understand a tag, it ignores it. Thus, if you use an iframe (I'll use IFRAME as an example throughout this answer) in your document, make sure that you have content in the iframe tag for any browser that decides to ignore the tag. Just because a browser supports something like IFRAME doesn't mean that the user hasn't disabled that support. The key here is to make sure your write your HTML in such a way as it degrades gracefully in older browsers.

Remember that HTML only *suggests* a layout for your page. It is a markup language to imply certain characteristics about the data on your page. There's nothing wrong with designing a page with a visual browser in mind, but you have to make sure you write your markup intelligently so non-visual browsers could also use it. Take a look at my website in your favorite browser, then in Lynx. You don't see any less content. I use advanced features of Javascript such as dynamically assigning styles to show and hide layers, but you can still view the content if a browser has Javascript disabled.

Continued in comment...

by jay eckles

Some tips to keep in mind:

ALWAYS use the alt attribute in image tags, and put information that serves as a substitute for what the image communicates. If the image is just meaningless decoration (like a rounded corner for a table), use "" as the alt text. If the image doesn't download, the alt text will be avaialble. If the browser is non-visual, the alt text will be available. Most of all, you have no idea why your image might not be displayed, but using alt text ensures that your content is still delivered.

Always put content in elements that require a closing tag. For instance, put content between your and tags so browsers that do not support a certain tag can still receive appropriate content. Avoid the temptation to put a message saying "Your browser does not support the X tag". They'll already know that, since the content isn't being displayed. Instead, if you cannot put substitute content inline, provide a link to a page where they can get the substitute information. If you're using IFRAME, do something like this:

Use CSS to provide formatting and positioning to your text. Don't use FONT tags; instead, define styles for the appropriate elements or for classes (you can assign a class to a bit of text using a div or span tag).

If you want more information on writing accessible and valid HTML, please email me.

Good luck.

Jay Eckles
www.jayeckles.com

by ian boothby

All points accepted Jay, but it does contribute to a lot more writing!

I guess it's the old answer I'm looking for - I'll just have to make my own decision and decide on the best balance!

Cheers

This discussion is closed to new replies.