After several discussions with people making websites that sometimes quite frankly apore me, I have decided to write this article on using valid markup for your projects.

I recently had a discussion with a web designer, the main jist of what they said being:

I was told not to bother using xhtml, it's never going to be needed;
I didn't fill in the ALT tags because the client said they didn't want them;
The basic idea being: [i:2c8bfe648e]I'm a web designer, Im not concerned that my client has an accessible site, I just want my cash.[/i:2c8bfe648e]

Ok, to start with, try using valid HTML 4.01. Not only will you then find your pages start working right in every browser, you will find the source code a lot easier to read through when updating.

Once you feel you have the hang of writing in valid HTML 4.01, then trying using XHTML. Start with Transititional XHTML 1.0, again to get the hang of it, then try writing in XHTML 1.0 Strict, and then try XHTML 1.1.


[b:2c8bfe648e]Why should I use XHTML over HTML do you ask?[/b:2c8bfe648e]

Well.... whilst using valid coding brings hundreds of direct benefits to the visitors of your site, switching from HTML to XHTML does not. However!

[b:2c8bfe648e]-[/b:2c8bfe648e] XHTML is easier to maintain

[b:2c8bfe648e]-[/b:2c8bfe648e] XML syntax rules are far more rigorous than HTML. As a result, XHTML makes authors work more precisely, having to address issues such as:
[list:2c8bfe648e]
[*:2c8bfe648e]all elements and attribute names must appear in lower case
[*:2c8bfe648e]all attribute values must be quoted
[*:2c8bfe648e]non-Empty Elements require a closing tag
[*:2c8bfe648e]empty elements are terminated using a space and a trailing slash
[*:2c8bfe648e]no attribute minimization is allowed
[*:2c8bfe648e]in strict XHTML, all inline elements must be contained in a block element
[/list:u:2c8bfe648e]
[b:2c8bfe648e]-[/b:2c8bfe648e] The margin for errors in HTML is much broader than in XHTML, where the rules are very clear. In HTML, case, quotes, termination of many elements and uncontained elements are allowed and commonplace. As a result, XHTML is easier to author and to maintain, since the structure is more apparent and problem syntax is easier to spot.
[b:2c8bfe648e]-[/b:2c8bfe648e] XHTML is XSL ready
[b:2c8bfe648e]-[/b:2c8bfe648e] XHTML is easier to teach and to learn
[b:2c8bfe648e]-[/b:2c8bfe648e] When the new version of XHTML becomes a recommendation, XHTML 1.0 documents will be easily upgradable to this new version, to allow to take advantages of its exciting new features. It's likely that an XSLT style sheet will be available by then to help you move your XHTML 1.0 (strict) documents to XHTML 2.0 documents.

It provides for a page that is accessible to all, perfectly coded. It is 100% fine, not just the majority of it.

I work for a company that provides online development to other companies and induvidals and our overall biggest priority is building a fully valid and accessible webpage, not just using the correct coding, but making sure those who are disabled in some form can still access the website.

With the way it's going, various companies have been taken to court over providing inaccessible sites, it can actually fall out the Discrimination act in both UK and US law.

Simple things like making sure the page can still be read if colours are turned off, that images don't flash at a certain frequency, filling all alt tags with good content...

It may be the perogative of a client to decide overall, but as their web developer you should reinforce the point of validty and accessibility. We here would suggest you tell them about the issues of accessibility and such causes online, and that it is a very good idea to comply to these standards.