Just as a short follow-up to Why XHTML?, I thought I’d give you some read-worthy links to posts about it, and also bring up companies’ attitude towards it.
What I wonder is if companies really care about the level and quality of interface code they deliver, no matter if it’s HTML or XHTML.
As long as it doesn’t break miserably, it doesn’t matter. I used the Blogger service before swithcing to WordPress, and Blogger were always very quick to answer support mails, and during outages they seemed to work hard and efficiently to fix it.
With that said, I got a little saddened by something they wrote in a reply to my question about that the comment interface didn’t generate valid XHTML. The thing is, their templates (at least the ones I used) were coded using XHTML 1.0 Strict, so naturally I wanted my pages containing comments to be well-formed too.
However, unless it
is actually breaking functionality somewhere in Blogger or causing true
accessibility issues, it will likely be treated with a low-priority.
I think this symbolizes the general attitude of many companies: if it doesn’t break, it isn’t really that important if it is correct.
Let’s fall back on forgiving web browsers instead. But this might turn into a problem if browsers in the future will demand correct code to render it correctly.
What do you think? Are the companies right when it comes to this prioritizing, or is this exactly the attitude that holds the web back from evolving?